1 + 2 + 3 + 4 + | Object parameter for Class Student: + -mixin:alias -filter:alias ... + {-superclass:alias ::nx::Object} ... + -attributes:alias _:initcmd,optional |
Index: doc/next-tutorial.html =================================================================== diff -u -re87fe21651b656a0aebe214c6d7ca1866d5b2289 -r57570354bfebc1bc24f1ba3d7976c44b2c2bd3e9 --- doc/next-tutorial.html (.../next-tutorial.html) (revision e87fe21651b656a0aebe214c6d7ca1866d5b2289) +++ doc/next-tutorial.html (.../next-tutorial.html) (revision 57570354bfebc1bc24f1ba3d7976c44b2c2bd3e9) @@ -818,7 +818,7 @@
The definition of the stack in Listing 3 +
The definition of the stack in Listing 2 is following the traditional object oriented approach, found in practically every object oriented programming language: Define a class with some methods, create instances from this class, and use the @@ -2069,12 +2069,13 @@ instance variables of objects are initialized and how these objects could be parameterized.
Syntactically, object and method parameters are the same, although -there are certain differences (e.g. some parameter options are only -applicable for objects parameters, the list of object parameters is -computed dynamically, object parameters are often used in combination -with special setter methods, etc.). Consider the following example, -where we define two application classes with a few attributes.
Syntactically, object parameters and method parameters are the same, +although there are certain differences (e.g. some parameter options +are only applicable for objects parameters, the list of object +parameters is computed dynamically from the class structures, object +parameters are often used in combination with special setter methods, +etc.). Consider the following example, where we define the two +application classes Person and Student with a few attributes.
1 + 2 + 3 + 4 + | Object parameter for Class Student: + -mixin:alias -filter:alias ... + {-superclass:alias ::nx::Object} ... + -attributes:alias _:initcmd,optional |
More detailed definition of the object parameter types comes here.
In one of the previous sections, we defined scripted (application +defined) checker methods on a class named nx::Slot. In general NX +offers the possibility to define value checkers not only for all +usages of parameters but as well differently for method parameters or +object parameters
Still Missing