X-Git-Url: https://ocean-lang.org/code/?p=ocean-D;a=blobdiff_plain;f=00-TODO;h=8c0efc77bafe710ae709f0a582f47232ed876ca7;hp=7aa2fd3559095b9f0121fdf50dc53b8942ec85c9;hb=6830d7faa83def1431a9f5a981c008eeb272a5f6;hpb=83f7f2eae2f646ef67bb024ec50d1a3a4443de04

diff --git a/00-TODO b/00-TODO
index 7aa2fd3..8c0efc7 100644
--- a/00-TODO
+++ b/00-TODO
@@ -1,33 +1,82 @@
 This is a living document - delete things when done.  Avoid discussion.
 
-Current version (Jamison Creek)
-- more operators: and then, or else, if else
-- global consts
+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
 - structs
-   - const or variable fields
-   - initial value
+   - const fields
    - anonymous field - array or struct (or pointer to these)
+      multiple anon struct ar allowed if they don't conflict
    - [] can apply to anon array field
    - anon struct field gets fields interpolated
 
-Next version ??
-
 - 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.
 - 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
-   - overloaded or pure
+   - pure, loaded, overloaded, augmented
+   - owned: once, counted, collected
+   - shared or thread-local
 - array slice
-- char, string search
+- 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.
 
-Much later
+Next version (Govetts Creek):
 - functions and procedures
+- Finalize what a "main" program looks like.
+
+Much later
 - per-field attributes
+    constant, stable, add-only, read-only, mutable, owned, borrowed, dependant, pure
 - records
 - enum
 - classes
-- imports and exports
-- closuers, threads, co-routines
+   - constructors and destructors - or "after" ??
+   - vtables, fat pointers, list of approaches
+- operators as interface methods
+- interfaces, inheritance
+- modules, imports and exports
+- closures, threads, co-routines, generators
+- introspection / reflection ?
+      e.g. support serialization
+      find function given a string holding the name
+      measure coverage, adjust based on performance metrics
+      auto-create mock objects
+      Is this just parsing the details in the obj file?
+- % formatting
+- string / slice / strbuf
+- parsing library - sscanf equiv, regexp, LALR
+- FFI
+- GTK
+- sockets / http / HTML
+- parameterised types, and dependant types
+- message passing primitives
+- overloading for numbers
+- exceptions ??
+- ensure list_head type concept can work
+- "union" type ??
+- pattern matching for destructuring??
+- casts??
+- typeswitch?
+- iso suffixes for number?
+- foreach?
+- case fall-through or go-to
+- break/continue or "next","last"
+- algebraic types