X-Git-Url: https://ocean-lang.org/code/?p=ocean-D;a=blobdiff_plain;f=00-TODO;h=13ea9e62f3a11c1d1ef56232b3fc0c2ac506efb5;hp=68717a49d4043be38af90df115c63a17539735c6;hb=509e0c8cd5c64e608032aa95a51dd5096185c338;hpb=da2b05008783a3fa1c92f546e237703237129c71 diff --git a/00-TODO b/00-TODO index 68717a4..13ea9e6 100644 --- a/00-TODO +++ b/00-TODO @@ -1,30 +1,51 @@ This is a living document - delete things when done. Avoid discussion. Current version (Cataract Creek) -- use precedence levels for expressions +- 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 +- 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. Next version (Govetts Creek): - functions and procedures