updates

[ocean-D] / 00-TODO

diff --git a/00-TODO b/00-TODO
index 8c0efc77bafe710ae709f0a582f47232ed876ca7..25b8eb127dca08f3154a57a45e83ad956ad388aa 100644 (file)
--- a/00-TODO
+++ b/00-TODO
@@ -1,29 +1,48 @@
 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
-   - [] can apply to anon array field
-   - anon struct field gets fields interpolated
+      multiple anon struct are allowed if they don't conflict
+      no - transparent fields!  They still have a name, but you can
+      look through it.
+   - [] can apply to transparent array field
+   - transparent struct field gets fields interpolated
+
+   - How to give attributes? just say the word?
+       struct foobar:
+               x:content  transparent
+               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 )
+
+   I think that last works. () might almost be optional
+     .foo=a
+   is an expression means a structure with a .foo field assined to 'a'
+     [3] = 2
+   is an array for at least 4 elements with 4th set to 2.
+
 - 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
@@ -36,7 +55,6 @@ Current version (Cataract Creek)
 
 - 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
@@ -46,14 +64,20 @@ Much later
 - per-field attributes
     constant, stable, add-only, read-only, mutable, owned, borrowed, dependant, pure
 - records
-- enum
+- enum / set
 - classes
    - constructors and destructors - or "after" ??
+     destructors, which can be declared inline
    - vtables, fat pointers, list of approaches
 - operators as interface methods
+     + - * / etc make an arith interface add sub mult div
 - interfaces, inheritance
 - modules, imports and exports
+     public(version) on types, fields etc
 - closures, threads, co-routines, generators
+- generics/templates.  These should be just a compile-time
+  decision.  Same code can be called with suitable methods passed, or
+  recompiled in the new context and then optimised.
 - introspection / reflection ?
       e.g. support serialization
       find function given a string holding the name