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 @@

2.5. Interceptors

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.

+filters. The primary difference in NX is the naming, since NX abandons +the prefix "inst" from the names of instance specific method, but uses +the the modifier 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.

2.5.1. Register Mixin Classes and Mixin Guards

@@ -4481,7 +4482,8 @@

2.6.7. List definition of scripted object specific methods

While XOTcl uses different names for info options for objects and -classes (using the prefix "inst"), the names in NX are the same.

+classes (using the prefix "inst" for instance specific method), NX +uses for object specific method the modifier object.

Index: doc/next-migration.txt =================================================================== diff -u -r9be6ce36ba1fcc60da1f968ce4008c0b139afbc7 -r417e9e54ae7b0af1ee69c34525ad99c2beabedf8 --- doc/next-migration.txt (.../next-migration.txt) (revision 9be6ce36ba1fcc60da1f968ce4008c0b139afbc7) +++ doc/next-migration.txt (.../next-migration.txt) (revision 417e9e54ae7b0af1ee69c34525ad99c2beabedf8) @@ -1591,15 +1591,16 @@ 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. +filters. The primary difference in NX is the naming, since NX abandons +the prefix "inst" from the names of instance specific method, but uses +the the modifier +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 class object. +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. ==== Register Mixin Classes and Mixin Guards @@ -2039,7 +2040,8 @@ ==== List definition of scripted object specific methods While XOTcl uses different names for info options for objects and -classes (using the prefix "inst"), the names in NX are the same. +classes (using the prefix "inst" for instance specific method), NX +uses for object specific method the modifier +object+. [options="header",cols="asciidoc,asciidoc",frame="none",valign="middle"] |======================