Index: doc/next-migration.html =================================================================== diff -u -rc6816ddd8f161680aa286d56235737f1fc27fe79 -r3d145fa523334bae381b61747a7c6178021e78d3 --- doc/next-migration.html (.../next-migration.html) (revision c6816ddd8f161680aa286d56235737f1fc27fe79) +++ doc/next-migration.html (.../next-migration.html) (revision 3d145fa523334bae381b61747a7c6178021e78d3) @@ -1539,7 +1539,7 @@ to variables (called parametercmd and instparametercmd). The accessor functions are used normally internally when object-specific parameters are defined (see Section 3.4).

-

In NX forwarders are called forward. NX does not provide an public +

In NX forwarders are called forward. NX does not provide a public available method to define variable accessors like parametercmd in XOTcl, but use internally the Next Scripting Framework primitive nsf::method::setter when appropriate.

@@ -2465,8 +2465,7 @@ an accessor is a method with the same name as the variable. In XOTcl, every parameter defined as well automatically a same-named accessor method, leading to potential name conflicts with other method names.

-

In the examples below we show the definition of configurable an -non-configurable instance variables using variable and property +

In the examples below we show the definition of configurable a non-configurable instance variables using variable and property respectively.

init, NX follows a more declarative approach. Often, classes have superclasses, which often want to provide their own instance variables and default values. The declarative approach from -NX solves this via inheritance, while an procedural approach via +NX solves this via inheritance, while a procedural approach via assign statements in the constructor requires explicit constructor calls, which are often error-prone. Certainly, when a user prefers to assign initial values to instance variables via explicit assign @@ -3116,7 +3115,7 @@ objects, which are an extension to the -slots already available in XOTcl. While very for every property in NX, a slot object is created, for performance reasons, not every variable has a slot associated.

-

When an property is created, NX does actually three things:

+

When a property is created, NX does actually three things:

  1. @@ -6428,7 +6427,7 @@ XOTcl 1 NSF does not allow one to redefined a pre-existing command (e.g. "set") with an object and vice versa. Like in XOTcl 1, preexisting objects and classes con be redefined (necessary for -reloading objects/classes in an running interpreter).

+reloading objects/classes in a running interpreter).

3.2.5. Info heritage