Index: TODO
===================================================================
diff -u -r475bb7279b7df4c5bbdb90986ec3dfd988cf8776 -r6f127ecf78a90478bc889376cb0cb0c05d55b451
--- TODO	(.../TODO)	(revision 475bb7279b7df4c5bbdb90986ec3dfd988cf8776)
+++ TODO	(.../TODO)	(revision 6f127ecf78a90478bc889376cb0cb0c05d55b451)
@@ -1198,6 +1198,9 @@
 - make sure to test next to non-existing shadowed 
   method in connections with filters and unknwon handlers
 
+- documented incompatiblity of object-invocation via method
+  interface (due to ensemble objects) in migration guide
+
 TODO: 
 
 - check "my" vs. "nsf::dispatch" in xotcl2.tcl
@@ -1218,12 +1221,7 @@
 
 - aliases on procs are a problem, when upvar is used (see info default/instdefault in xotcl2.tcl)
 
-- add incompatiblity to migration guide
-  Foo slot ints eval { set :incremental 1; :optimize}
-  should become:
-  Foo::slot::ints eval { set :incremental 1; :optimize}
 
-
 - interfaces in documentation for slots (see for more details 
   ::nx::Class#superclass in nx.tcl).
 - nameing
Index: doc/next-migration.html
===================================================================
diff -u -re849d060161385466c782e46c19344428934cd7f -r6f127ecf78a90478bc889376cb0cb0c05d55b451
--- doc/next-migration.html	(.../next-migration.html)	(revision e849d060161385466c782e46c19344428934cd7f)
+++ doc/next-migration.html	(.../next-migration.html)	(revision 6f127ecf78a90478bc889376cb0cb0c05d55b451)
@@ -1394,15 +1394,33 @@
 <h2>Incompatibilities between XOTcl 2.0 and XOTcl 1.*</h2>
 
 <h3>Resolvers</h3>
-<p>The resolvers of the Next Scripting Framework are used as well
-within XOTcl 2.0. When names starting with single colons are used in
-XOTcl 1.* scripts, conflicts will arise.
-</p>
 
+<p>The resolvers (variable resolvers, function resolvers) of the Next
+Scripting Framework are used as well within XOTcl 2.0. When names
+starting with single colons are used in XOTcl 1.* scripts, conflicts
+will arise.  </p>
+
+<h3>Calling objects like methods</h3>
+
+<p>Since the next framework uses a different handling of objects
+registered as methods (so called ensemble objects), sub-objects can't
+be called in the same way as before. In XOTcl 1.*, it was possible to
+call e.g. a method <code>foo</code> of the slot object
+<code>Foo::slot::ints</code> via
+<ul><li><code>Foo::slot::ints foo ...</code> or via
+  <li><code>Foo slot ints foo ...</code>
+</ul>
+Now, only the first form
+has the same semantic as before. In the second form (call of objects
+via method) has now the ensemble object semantics, <code>self</code>
+of <code>foo</code> is now the calling object <code>Foo</code>.
+
+
 <h3>Slots</h3>
-<p>All slots are now always next-scripting objects.
-</p>
 
+<p>All slot objects (also those in XOTcl) are now always
+next-scripting objects of baseclass ::nx::Slot </p>
+
 <h3>Obsolete commands</h3>
 
 <p>Parameterclasses were rarely used and have been replaced by the more
@@ -1415,12 +1433,6 @@
 1.*. For example, the requiredness of slots in XOTcl was just a
 comment, while Next enforces it. </p>
 
-<h3>Different results</h3>
-<ul>
-  <li>none?
-</ul>
-
-
 <h3>Exit Handlers</h3>
 <p>
 The exit hander interface changed from a method of
@@ -1435,6 +1447,6 @@
 
 <hr>
 <address></address>
-<!-- hhmts start --> Last modified: Wed Aug 25 10:05:42 CEST 2010 <!-- hhmts end -->
+<!-- hhmts start --> Last modified: Tue Aug 31 10:41:17 CEST 2010 <!-- hhmts end -->
 </body>
 </html>