doc tweaks

docs/source/building.rst

@@ -89,7 +89,7 @@ a successful compilation. This will load your program and the symbol and breakpo
 
 Continuous compilation mode
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
-Almost instant compilation times (<0.1 second) can be achieved when using the continuous compilation mode.
+Almost instant compilation times (less than a second) can be achieved when using the continuous compilation mode.
 Start the compiler with the ``-watch`` argument to enable this.
 It will compile your program and then instead of exiting, it waits for any changes in the module source files.
 As soon as a change happens, the program gets compiled again.

docs/source/index.rst

@@ -151,7 +151,7 @@ Design principles and features
   the compiled program in an emulator and provide debugging information to the emulator.
 - The compiler outputs a regular 6502 assembly source code file, but doesn't assemble this itself.
   The (separate) '64tass' cross-assembler tool is used for that.
-- Goto is usually considered harmful, but not here: arbitrary control flow jumps and branches are possible,
+- Arbitrary control flow jumps and branches are possible,
   and will usually translate directly into the appropriate single 6502 jump/branch instruction.
 - There are no complicated built-in error handling or overflow checks, you'll have to take care
   of this yourself if required. This keeps the language and code simple and efficient.

docs/source/todo.rst

@@ -2,28 +2,6 @@
 TODO
 ====
 
-
-Fixes
-^^^^^
-variable naming issue::
-
-    main {
-
-        sub start() {
-            for A in 0 to 10 {
-                ubyte note1 = 44
-                Y+=note1
-            }
-            delay(1)
-
-            sub delay(ubyte note1) {        ; TODO: redef of note1 above, conflicts because that one was moved to the zeropage
-                A= note1
-            }
-        }
-    }
-
-
-
 Memory Block Operations integrated in language?
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
@@ -49,7 +27,6 @@ More optimizations
 Add more compiler optimizations to the existing ones.
 
 - on the language AST level
-- on the StackVM intermediate code level
 - on the final assembly source level
 - can the parameter passing to subroutines be optimized to avoid copying?
 
@@ -57,6 +34,7 @@ Add more compiler optimizations to the existing ones.
   this requires rethinking the way parameters are represented, simply injecting vardecls to
   declare local variables for them is not always correct anymore
 
+- working subroutine inlining (taking care of vars and identifier refs to them)
 
 Also some library routines and code patterns could perhaps be optimized further