Less use of eval( in unit tests

diff --git a/basis/classes/struct/struct-tests.factor b/basis/classes/struct/struct-tests.factor
index 765af7e3cab0c78b9bbbbb19cd7922c7f2fc19b5..56d1cec21d93e46e3bfb4f64858f39186439e84c 100644 (file)
--- a/basis/classes/struct/struct-tests.factor
+++ b/basis/classes/struct/struct-tests.factor
@@ -535,12 +535,11 @@ STRUCT: struct-1-union { a int initial: 0 } ;
 " ]
 [ \ struct-1-union [ see ] with-string-writer ] unit-test
 
-
 ! Bug #206
-STRUCT: going-to-forget { a uint } ;
+STRUCT: going-to-redefine { a uint } ;
 [ ] [
-    "IN: classes.struct.tests TUPLE: going-to-forget b ;" eval( -- )
+    "IN: classes.struct.tests TUPLE: going-to-redefine b ;" eval( -- )
 ] unit-test
-[ f ] [ "USING: classes.struct.tests kernel ; M\\ going-to-forget clone" eval( -- obj ) ] unit-test
-[ f ] [ "USING: classes.struct.tests classes.struct kernel ; M\\ going-to-forget struct-slot-values" eval( -- obj ) ] unit-test
+[ f ] [ \ going-to-redefine \ clone method ] unit-test
+[ f ] [ \ going-to-redefine \ struct-slot-values method ] unit-test