This is a living document - delete things when done. Avoid discussion.
Current version (Cataract Creek)
-- use precedence levels for expressions
- 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
+- integers, unsigned, bitfield, float, double?
- pointers
- owned or borrowed
- pure, loaded, overloaded, augmented
- owned: once, counted, collected
+ - shared or thread-local
- array slice
- array buffer - can be added to and grows.
- char, string search, regexp search
- 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