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.
+Scripting Framework are used as well within XOTcl 2.0. When variable names +or method names starting with a single colon are used in XOTcl 1.* scripts, conflicts +will arise with the resolver. These names must be replaced.Since the next framework supports the so-called ensemble objects,
-which eas the definition of submethods substantially, objects
+which ease the definition of submethods substantially, objects
registered as methods have different semantics. In XOTcl 1.*, it was
possible to call e.g. a method foo of the slot object
Foo::slot::ints via the following two interfaces the same way:
@@ -1450,23 +1450,23 @@
All slot objects (also those in XOTcl) are now always
-next-scripting objects of baseclass ::nx::Slot.
-The name of the experimental default-setter initcmd was
-changed to defaultcmd.
-
All slot objects (also XOTcl slot objects) are now next-scripting
+objects of baseclass ::nx::Slot. The name of the
+experimental default-setter initcmd was changed to
+defaultcmd. Code directly working on the slots objects
+has to be adapted.
Parameterclasses were rarely used and have been replaced by the more +
Parameter-classes were rarely used and have been replaced by the more
general object parameterization. Therefore, cl info
parameterclass has been removed.
The Next Scripting Framework performs stronger checking than XOTcl -1.*. For example, the requiredness of slots in XOTcl was just a -comment, while Next enforces it.
+1.*. For example, the requiredness of slots in XOTcl 1.* was just a +comment, while XOTcl 2.* enforces it.@@ -1479,6 +1479,6 @@