This is a living document - delete things when done. Avoid discussion.
Current version (Cataract Creek)
-- Warn when left-recursive symbols appear elsewhere, other than at the end
- of a production. Might have to special-case Newlines.
-- parser not to get into ERROR infinite loop
-- sort 'virtual' symbols to end
-- allow $xy instead of $3. Chooses shortest bodysym with xy in that order
- $xy_2 gives the second one
-- allow $TERM terminals to be listed. If so, extras are errors
+- functions to return type with 'use'
+- functions to return structure with name assignment - bare 'use'?
+- '?' prefix operator returns Boolean
+- reference to struct (@foo), with @new, @free, @nil
+- more number types, no units yet
+
+Later
+- string manipulation
+- file i/o
+- enum
+- basic methods
- structs
- - const fields
+ - const fields ... what does that mean? Assign once as initialization?
+ Can be used for array size? What else?
- anonymous field - array or struct (or pointer to these)
- multiple anon struct ar allowed if they don't conflict
+ multiple anon struct are allowed if they don't conflict
- [] can apply to anon array field
- anon struct field gets fields interpolated
+ - anon fields have no name before the :, so
+ struct foobar:
+ :content
+ size:number
+
- manifest values for arrays and structs [a,b,c]
or [.foo=a, .bar=b] or [ [1]=a, [2]=b]
That last doesn't parse easily, unless we require tags... not a good idea.
[ .[1] = a, .[2] = b ] ?? Maybe.
+ or () to group, [] for index. To (.foo=a) ( [1] = b )
- yet more operators
<< >> #
bit-ops & | ~ &~
op=
-- split values so I can have an array of just the value (1 byte for u8)
- integers, unsigned, bitfield, float, double?
- pointers
- owned or borrowed
- allow "do stuff" as a stand-alone statement (scope)
- 'use' labels *must* appear in case statements.
-- re-read parsergen lit-doc and make sure it is still coherent.
Next version (Govetts Creek):
- functions and procedures
code / ocean-D / blobdiff