diff --git a/compiler/res/version.txt b/compiler/res/version.txt
index 9fb9399cc..bf77d5496 100644
--- a/compiler/res/version.txt
+++ b/compiler/res/version.txt
@@ -1 +1 @@
-4.2-SNAPSHOT
+4.2
diff --git a/examples/test.p8 b/examples/test.p8
index 7295c4d5c..1111c8dc0 100644
--- a/examples/test.p8
+++ b/examples/test.p8
@@ -1,42 +1,20 @@
+%import c64lib
+%import c64graphics
 %import c64textio
 ;%import c64flt
 ;%option enable_floats
-%zeropage kernalsafe
+%zeropage basicsafe
 
 
 main {
 
-    struct Color {
-        ubyte red
-        ubyte green
-        ubyte blue
-    }
-
-    sub start() {
-
-        ubyte ub = 9
-        uword yy = 9999     ; this is okay (no 0-initialization generated) but... the next:
-        uword xx = ub           ; TODO don't generate xx = 0 assignment if it's initialized with something else...
-        uword zz
-
-        Color purple = [1,2,3]
-
-        uword x1
-        uword x2
-
-        word dx = x2 - x1 as word
-
-        ;ub++
-        ;xx++
-        ;yy++
-        ;zz++
-
 ;asmsub  clear_screen (ubyte char @ A, ubyte color @ Y) clobbers(A)  { ...}
 ; TODO dont cause name conflict if we define sub or sub with param 'color' or even a var 'color' later.
 
 ;   sub color(...) {}
 ;   sub other(ubyte color) {}    ; TODO don't cause name conflict
 
-    }
 
+    sub start()  {
+    }
 }