doc

codeOptimizers/test/TestOptimizers.kt

@@ -1,18 +0,0 @@
-package prog8tests
-
-import org.junit.jupiter.api.Disabled
-import org.junit.jupiter.api.Test
-import org.junit.jupiter.api.TestInstance
-import kotlin.test.fail
-
-
-@TestInstance(TestInstance.Lifecycle.PER_CLASS)
-class TestOptimizers {
-
-    @Test
-    @Disabled("for future implementation")
-    fun dummy() {
-        fail("dummy")
-    }
-
-}

codeOptimizers/test/readme.txt

@@ -0,0 +1,2 @@
+Unittests for things in this module are located in the Compiler module instead,
+for convenience sake - and to not spread the test cases around too much.

compilerInterfaces/test/readme.txt

@@ -1,2 +1,2 @@
 Unittests for things in this module are located in the Compiler module instead,
-for convenience sake.
+for convenience sake - and to not spread the test cases around too much.

docs/source/syntaxreference.rst

@@ -357,7 +357,7 @@ The ``&`` (address-of operator) used in front of a data type keyword, indicates
 should be allocated by the compiler. Instead, the (mandatory) value assigned to the variable
 should be the *memory address* where the value is located::
 
-	&byte BORDERCOLOR = $d020
+    &byte BORDERCOLOR = $d020
     &ubyte[5*40]  top5screenrows = $0400        ; works for array as well
 
 

docs/source/todo.rst

@@ -5,6 +5,14 @@ For next compiler release (7.2)
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 - fix the asm-labels problem (github issue #62)
 - find a way to optimize asm-subroutine param passing where it now sometimes uses the evalstack?
+- analyze (and fix?): TODO why are these bigger now than before the var-initializer optimization:
+    ;    wizzine
+    ;    wormfood
+    ;    cube3d-float (THIS ONE IS A LOT BIGGER!!)
+    ;    cube3d-sprites
+    ;    textelite
+    ;    etc.
+
 
 
 Blocked by Commander-x16 v39 release