2009-03-19 * Release of XOTcl 1.6.3 2009-03-19 - removed references to 1.6.2 2009-03-04 - re-enable small optimization - factor out common code - fix compatibility with Tcl 8.4 - bump version number to 1.6.3 2009-03-03 - simplify semantics of MixinSeekCurrent and FilterSeekCurrent, improve speed - remove necessity to have tclCompile.h - improve documentation 2009-03-02 - some small performance improvements (use CreateHashEntry instead of FindHashEntry, remove unneded argument, improve order of long and expressions) - some code cleanup - new methods, when compiled with tcl 8.5; + MakeProcError (producing error messages from xotcl methods) + PushProcCallFrame (compile method to byte-code) The new support allows to call code at the begin of a proc without using the old approach based on :xotcl::initProcNS 2009-02-19 - add comments to var resolution tests for objects without namespaces - fixed reference counting - removed temporary hacks - added CONST to several functions - added relative namespace handling 2009-02-18 , sobernig@wu-wien.ac.at - added Stefan's work for namespace resolvers - fixed a memory leak for "obj exists" due to the changes - found another memory leak, when e.g. "::info" is added as an alias and "info exists" is tested against non-existing vars 2009-01-19 - Finish work on deletion of user-metaclasses - commenting existing and potential usage of namespace resolvers 2008-12-01 * Correct deletion of user-metaclasses: Deletion of user-metaclasses could lead to undestroyable objects, since the instances of the user-metaclasses were reclassed to ::xotcl::Object instead of ::xotcl::Class. * extend regression test for such situations 2008-11-02 * Release of XOTcl 1.6.2 2008-11-01 * added command ::xotcl::finalize This command has the only purpose to delete all objects and classes of an interpreter in a multi-threaded environment at a safe time. Background: when XOTcl is used in a threaded environment such as for example in AOLserver, one has to take care that the deletion of objects and classes happens in a safe environment, where the XOTcl destructors (destroy methods) are still able to run. Without ::xotcl::finalize the deletion happens in Tcl_FinalizeThread(), after thread cleanup (where e.g. the thread local storage is freed). This can lead to memory leaks in AOLserver, which allocates e.g. some structures on demand, but since this happens after cleanup, it will leak. A simple ns_log in a destructor might lead to this problem. The solution is to call ::xotcl::finalize in the "delete trace" in AOLserver (as it happens in OpenACS). Note, that ::xotcl::finalize is not intended for application programs. * some code cleanup 2008-10-17 * handle nonposargs in method "copy" properly * extend regression test for copy * added " mixinof -closure ?pattern?" Query the objects for which is used as a per-object-mixin (directly or indirectly) * extended regression test for mixinof * updated documentation 2008-09-11 * Implement proper downgrading of Classes to Objects: In cases where a class ::C is created, which is later downgraded to an object ::C (either via "::C class ::xotcl::Object" or via "::xotcl::Object ::C"), earlier versions of XOTcl were to liberal. The major problem is to invalidate all places, where ::C might be used as a class, and were only classes are allowed (e.g. mixin chains, precedence orders). The new version does not allow downgrading via the class method and does a destroy/create instead of a recreate when a same-named class existed before. * reset mixin order for per-object mixins, when the superclass of a class is deleted, which is used as per-object mixin * extended regression test * Updating and improving documentation 2008-06-24 * Release of XOTcl 1.6.1 2008-06-23 * remove pattern argument from "info class" * additional argument for "info precedence": "-intrinsic" Syntax: info precedence ?-intrinsic? ?pattern? If "-intrinsic" is specified, only the classes of the superclass type hierarchy are returnd. Otherwise, the precedence contains mixin classes as well. * Check results for guards to be boolean instead of int (now, guards are allowed to return e.g. "true") 2008-05-30 * updating language reference * Fix contents for %proc in forwarders in cases, where the forwarder was called via next and the argument list for next was provided. Previously, "next" was used for %proc. 2008-05-28 * make "info (inst)?forward -definition name" more robust (provide an error message, if is not given * New info subcommands "info parametercmd" and "info instparametercmd" * export *parametercmds in Serializer, use "-noinit" on slots as well 2008-05-26 * fixed bug in info instdefault, when the given argument name is an empty string. Example: X info instdefault crash "" var 2008-05-09 * used catch in the deprecated package xotcl::upvar-compat as suggested by Jeff Hobbs 2008-03-18 * allowed "abstract method" in additon to "abstract instproc" and "abstract proc" 2008-02-26 * xotcl.c: The double ;; chokes MSVC6 in the next line. (many thanks for Andreas Kupries for reporting) 2008-02-25 * Fix for "x configure -set"; many thanks to Rene Zamseil for reporting. 2008-02-24 * Release of XOTcl 1.6.0 2008-02-22: * Update of documentation 2008-02-21: * Clear XOTCL_MIXIN_ORDER_VALID flag unconditionally in MixinInvalidateObjOrders() for mixins (Neophytos had problems in naviserver; many thanks for reporting!) 2008-02-21: * Replaced Tcl_ObjSetVar2() with Tcl_SetVar2Ex() in nonposargs, since Tcl 8.5 seemed to optimize local variables away, if these not referenced directly from from Tcl. Tcl 8.5 seems to optimize proc-local variables away, which are not directly referenced by the Tcl proc body. In the following example, "ot" is set from C (via nonposargs, previously via Tcl_ObjSetVar2()) and consumed via C (from the db-driver, using :ot). SomeClass instproc foo {-ot} { #ns_log notice ot=$ot return [db_string [my qn check_type] { select 1 from acs_object_types where object_type = :ot } -default 0] } When the logging command is added, the statement works fine. When the logging command was deactivated, the variable ot was not seen from the consumer. By changing the variable setting command to Tcl_SetVar2Ex(), it works fine. 2008-02-08: * New info option "-closure" for "info instmixin" with -guards and -closure support * Extended test cases for "info instmixin" 2008-02-06: * Continued with info orthogonality change