Index: doc/next-migration.html =================================================================== diff -u -r28ec3c5d3415bd165871553fe29a19606ce21df8 -rffd6cbb63866d681fa99c6688c87868c3d7abf3c --- doc/next-migration.html (.../next-migration.html) (revision 28ec3c5d3415bd165871553fe29a19606ce21df8) +++ doc/next-migration.html (.../next-migration.html) (revision ffd6cbb63866d681fa99c6688c87868c3d7abf3c) @@ -973,7 +973,14 @@
-Much smaller Interface: The Next Scripting Language has a much +Significantly Improved Test Suite: The regression test suite of + Next Scripting Scripting framework contain now more than + 5.000 tests, and order of magnitude more than in XOTcl 1.6 +
++Much Smaller Interface: The Next Scripting Language has a much smaller interface (i.e. provides less predefined methods) than XOTcl (see Table 1), although the expressability was increased in NX. @@ -1029,15 +1036,6 @@
This comparison list compares mostly XOTcl 1 with NX, some features are also available in XOTcl 2 (2a, 2c 2d, 3, 4).
-Significantly improved test suite: The regression test suite of - Next Scripting Scripting framework contain now more than - 5.000 tests, and order of magnitude more than in XOTcl 1.6 -
-namespace eval mypackage { +namespace eval mypackage { - package require XOTcl 2.0 + package require XOTcl 2.0 - # Define a class using XOTcl - xotcl::Class C1 - C1 instproc foo {} {puts "hello world"} + # Define a class using XOTcl + xotcl::Class C1 + C1 instproc foo {} {puts "hello world"} - package require nx + package require nx - # Define a class using NX - nx::Class create C2 { - :public method foo {} {puts "hello world"} - } - }
One could certainly create object or classes from the different object systems via fully qualified names (e.g. using e.g. ::xotcl::Class or ::nx::Class), but for migration for systems without explicit @@ -6914,7 +6912,7 @@