nsf

Clone Tools
  • last updated 9 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
- nsf.c: experimental implementation of ::nsf::method::dispatch

- nsf.c: small performance improvements

- TODO: updated

- library/xotcl/library/comm/Connection.xotcl: Provide temporary workaround for Tcl bug #3401422; the NSF/NX/XOTcl2 test suite completes now under Tcl8.6b2.

- fixed substitution of logdir

- nsf.c: * removed warning about resetting cmd to 0 for private method invocations.

- minor optimizations

- nsf.c: * "private" implies now "protected". This means, setting "private" sets as well "protected", unsetting "protected" unsets "private" * make sure the "... method definition" of private methods is returned as "private" * extended regression test

- nsf.c * implemented NsfObjDispatchNRE and NsfObjDispatch * this fixed all issues of tcl8.6 and interp.test (xocomm still hangs in tcl 8.6)

- nsf.c: * factored out CmdIsNsfObject() for NRE handling with slave interpreters. * added flag ZSE_NRE_PROC for using nreProc instead of objProc

- minor documentation updates

- made nsf::my and nsf::object::dispatch available in the nx namespace

* removed "-local", "-system" and "-intrinsic" from plain dispatch (like e.g. "o1 -system method") * removed flag "-local" from nsf::object::dispatch

* added support for calling private methods via -local and filters * extended regression test for private + filters

- nsf.c: * allow protected and private methods to be used as filters * added regression tests * some cleanup in regression tests

- remove interp from MEM_COUNT implementation

- library/lib/test.tcl: Disarming [exit] for during the execution of test suites. I allow for using [exit] statements in (legacy) test suites, however, I provided for disabling them for the scope of Test->run() executions. During a test run, [exit] is replaced by a [return] trampoline. - library/xotcl/tests/xocomm.test: We now have a total MEM_COUNT of 0, which leaves us with a contains.test as the last patient (MC of 5). - tests/interp.test: minor cleanup

* added transparency for per-object private methods * extended regression test

- generic/nsf.c: Fixed the source of valgrind-reported mem leak: A pointer-reassignment situation in NsfAddParameterProc() orphaned the mem-block of a bare Tcl_Obj.

* per-thread MEM_COUNT tested with aolserver/naviserver * removed INTERP macros for MEM_COUNT (since we use now per-thread tables instead of per-interp tables as in the first implementation)

- nsf.c: * simplified permission handling * made private/protected mutual exclusive * extended regression test for private methods

- fix mutual exclusive tests for -intrinsic, -local, and -system - fix ref-counting

- reduce verbosity

- reduce verbosity

Merge branch '2.0.0-develop' of ssh://alice.wu-wien.ac.at/usr/local/src/git-repo/xotcl into 2.0.0-develop

- don't allow options "-intrinsic", "-local" and "-system" used in parallel

- generic/nsfAPI.h: Renamed the [::nsf::current next] subcommand to [::nsf::current nextmethod] - library/xotcl/library/xotcl2.tcl: Accordingly, the xotcl::self emulation maps [self next] to [current nextmethod] - tests/disposition.test, tests/methods.test, tests/submethods.test, tests/tcloo.test: Changed the few occurrences of [current next] to [current nextmethod] - tests/introspection.test: Added some basic tests on the expected behaviour of [::nsf::current nextmethod]

- generic/nsf.c: Provided a documentation block for CmdListRemoveDeleted()

- generic/nsf.c: For "tolerating" hidden objects, I verified the various occurrences of conitional branching based on the cmd's epoch counter. While most occurrences are not concerned (cmds of nested objects, or simply non-object commands), I identified three relevant spots: a) In NsfProcAliasMethod(), invalidating and rebinding the alias target command (including hidden objects as alias pointers) is based on the epoch counter; b) in MixinSearchProc() the lookup of mixed-in methods is affected; c) using CmdListRemoveEpoched() (as the name says), "deleted" commands are identified by looking at the cmd epoch and sorted out from mixin lists computed for precedence lists. I corrected cases b) and c), with the fixes being covered by accompanying tests; a) turned out to be consistent with alias rebinding behaviour for [rename]. While we could correct a) for hidden cmd awareness, this would have to be done for the likeminded alias + [rename] as well. - generic/nsf.c: Renamed CmdListRemoveEpoched() to CmdListRemoveDeleted() - tests/interp.test: Added tests on b) and c), as well as hiding globally namespaced procs and objects as alias targets (merely for documenting the behaviour).

- nsf.c: * added "/obj/ -intrinsic ..." similar to "/obj/ -system ..." * added "nsf::my /obj/ -intrinsic ..." similar to "/obj/ -intrinsic ..." * added "nsf::object::dispatch /obj/ -intrinsic ..." similar to "/obj/ -intrinsic ..." * extended regression test