Index: doc/next-migration.html =================================================================== diff -u -r9be6ce36ba1fcc60da1f968ce4008c0b139afbc7 -r417e9e54ae7b0af1ee69c34525ad99c2beabedf8 --- doc/next-migration.html (.../next-migration.html) (revision 9be6ce36ba1fcc60da1f968ce4008c0b139afbc7) +++ doc/next-migration.html (.../next-migration.html) (revision 417e9e54ae7b0af1ee69c34525ad99c2beabedf8) @@ -3355,14 +3355,15 @@
XOTcl and NX allow the definition of the same set of interceptors, namely class- and object-level mixins and class- and object-level -filters. The primary difference in NX is the naming, since NX -abandons the prefix "inst" from the method names.
Therefore, in NX, if a mixin
is registered on a class-level, it
-is applicable for the instances (a per-class mixin), and if
-and object mixin
is registered, it is a per-object mixin.
-In both cases, the term mixin
is used, in the second case
-with the modifier object
. As in all other cases, one can
-register the same way a per-object mixin on a class object.
objec
" for object specific methods.
+Therefore, in NX, if a mixin
is registered on a class-level, it is
+applicable for the instances (a per-class mixin), and if and object
+mixin
is registered, it is a per-object mixin. In both cases, the
+term mixin
is used, in the second case with the modifier
+object
. As in all other cases, one can register the same way a
+per-object mixin on a plain object or on a class object.
While XOTcl uses different names for info options for objects and -classes (using the prefix "inst"), the names in NX are the same.
object
.