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 @@
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. -
+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.
+ +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 foo
of the slot object
+Foo::slot::ints
via
+
Foo::slot::ints foo ...
or via
+ Foo slot ints foo ...
+self
+of foo
is now the calling object Foo
.
+
+
All slots are now always next-scripting objects. -
+All slot objects (also those in XOTcl) are now always +next-scripting objects of baseclass ::nx::Slot
+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.
-The exit hander interface changed from a method of @@ -1435,6 +1447,6 @@