Announcing XOTcl 1.6.6
*************************
Dear XOTcl Community,
We are pleased to announce the availability of XOTcl 1.6.6
Major changes relative to 1.6.5 are:
* improved 64-bit compatibility (expat)
* fixed minor memory leaks (info methods, forward error case)
* fixed potential cyclic dependencies via namespace imports
during cleanup
* fixed potential crash with var-traces being fired twice
* compatibility with Tcl 8.6b1
* fix for debian packaging
For more details about the changes, please consult the ChangeLog and
documentation. The planned next release will be 2.0.0
MORE INFORMATION
General and more detailed information about XOTcl and its
components can be found at http://www.xotcl.org
best regards
-gustaf neumann
On 26 Apr 2010, at 11:04, Stefan Sobernig wrote:
>
> Well, there is a slight difference between the [package] and TEA
> versioning schemes. While for [package] version numbers,
> compatibility is only indicated by the major version number (*1*.2.0
> vs. *1*.6.0), this is not a strict requirement for TEA version
> numbers. Here, as for the Tcl versioning (8.*4* vs. 8.*5* vs. 8.*6*
> vs 9), the minor number can indicate possible incompatibilities. I
> do not say that this distinction between [package] and TEA
> versioning makes any particular sense (apart from the Tcl stubs
> mechanism, probably). XOTcl has always followed the TEA approach
> from what i can tell and, while being very keen to avoid backward
> incompatibilities, does not give firm guarantees here.
Hm, I don't believe that is correct? In Tcl the minor number should
not indicate incompatibilities to the script at all. Basically all 8.0
scripts should run fine on 8.5. At least I can't think of any cases
where this has not been true, and that's the main reason why some TIPs
have been considered for 9.0 and not earlier.
--
Kristoffer Lawson, Co-Founder, Scred // http://www.scred.com/
In my 1.2 version of XOTcl (OSX) [info subclass] works in the
following way:
Class Foo
Class Bar -superclass Foo
Foo info class Bar
=> 1
However the current documentation says the parameter given is a
pattern and the fully qualified name is returned, or empty if no match
was found. Has this changed at some point? This would be quite an
incompatible change.
I actually prefer how it works on my installation. I want to
explicitly check if one class is a subclass of another, as objects,
not as patterns (patterns can be risky). And it's not actually clear
what is meant by 'pattern'. Foo is a class, Bar is a class, but Foo's
actual fully qualified name is ::Foo, so if I wanted an exact search
it should be against ::Foo, but will it also match 'Foo' (as desired)?
--
Kristoffer Lawson, Co-Founder, Scred // http://www.scred.com/