Index: TODO
===================================================================
diff -u -r2f793442bb2a7860acc5620811dcafddc43074d3 -rdf69a2729a1b835c38c170cb7439240089b86c6e
--- TODO	(.../TODO)	(revision 2f793442bb2a7860acc5620811dcafddc43074d3)
+++ TODO	(.../TODO)	(revision df69a2729a1b835c38c170cb7439240089b86c6e)
@@ -5240,54 +5240,8 @@
     /cls/ info syntax
   Use e.g. "/cls/ info lookup parameters create" instead
 
-nsf.c:
-- Let "/cls/ info mixinof -closure" return as well implicit mixin classes
-  to make it easier to determine class dependencies.
-
-  Example:
-
-     nx::Class create M0
-     nx::Class create M1 -superclass M0
-     nx::Class create M2 -superclass M1
-
-     nx::Class create C
-     nx::Class create D -superclass C
-
-     C mixin add M2
-
-     # M2 is mixed into C, and implicitely into D
-     #
-     # Since M2 is a subclass of M1, classes C and D depend as well 
-     # on M1 and M0, as seen in the heritage:
-
-     ? {C info heritage} ":M2 ::M1 ::M0 ::nx::Object"
-     ? {D info heritage} ":M2 ::M1 ::M0 ::C ::nx::Object"     
-
-     # previously, only "M2 info mixinof -closure" showed the
-     # mixin relations, even with "-closure", while M1 and M0 did not.
-
-     ? {M2 info mixinof -closure} "::C ::D"
-
-     # now these show the same relations (in this example).
-
-     ? {M1 info mixinof -closure} "::C ::D"
-     ? {M0 info mixinof -closure} "::C ::D"
-
-- adapt mixinof.test to the additional information
-- transform mixinof.test to newer style regression test with autoated object deletion
-
-========================================================================
-TODO:
-- update migration guide/tutorial
-
-- should we change "/obj/ info lookup syntax" to return obj and method as well?
-
-- use context-object for error messages of configure/new/create/recreate
-- remove // comments
-
-- what should happen with: "/class/ info mixin classes -heritage"
-- asymmetry between "/obj/ info lookup mixins" vs. "/obj/ info ?object? mixin classes"
-
+moved block here for keeping arguments
+=====
 - configure parameters: we have to cleanup
   Given:
 
@@ -5337,6 +5291,57 @@
      which is somewhat strange, since configure is not an object method.
      Probably: nsf-level command for handles.
 
+====
+
+nsf.c:
+- Let "/cls/ info mixinof -closure" return as well implicit mixin classes
+  to make it easier to determine class dependencies.
+
+  Example:
+
+     nx::Class create M0
+     nx::Class create M1 -superclass M0
+     nx::Class create M2 -superclass M1
+
+     nx::Class create C
+     nx::Class create D -superclass C
+
+     C mixin add M2
+
+     # M2 is mixed into C, and implicitely into D
+     #
+     # Since M2 is a subclass of M1, classes C and D depend as well 
+     # on M1 and M0, as seen in the heritage:
+
+     ? {C info heritage} ":M2 ::M1 ::M0 ::nx::Object"
+     ? {D info heritage} ":M2 ::M1 ::M0 ::C ::nx::Object"     
+
+     # previously, only "M2 info mixinof -closure" showed the
+     # mixin relations, even with "-closure", while M1 and M0 did not.
+
+     ? {M2 info mixinof -closure} "::C ::D"
+
+     # now these show the same relations (in this example).
+
+     ? {M1 info mixinof -closure} "::C ::D"
+     ? {M0 info mixinof -closure} "::C ::D"
+
+- adapt mixinof.test to the additional information
+- transform mixinof.test to newer style regression test with automated object deletion
+
+========================================================================
+TODO:
+- update migration guide/tutorial
+
+- should we change "/obj/ info lookup syntax /methodName/" to return obj and method as well?
+  (similar to "info method syntax /methodName/")
+- we could drop methods::object::info::objectparameter
+
+- remove // comments
+
+- what should happen with: "/class/ info mixin classes -heritage"
+- asymmetry between "/obj/ info lookup mixins" vs. "/obj/ info ?object? mixin classes"
+
 - fix error message for
   "C object mixin" returns 
   "::C mixin add|clear|delete|get|guard|set" and not