Xotcl January 2005

xotcl@alice.wu.ac.at

4 participants
4 discussions

Reference guide missing --noArgs
by Kristoffer Lawson 29 Jan '05

29 Jan '05

This feature of the [next] command is not documented in the reference guide. Thought it'd be good just to mention it :-) / http://www.fishpool.com/~setok/

1 0

windows binaries
by Gustaf Neumann 15 Jan '05

15 Jan '05

Forgot to mention: the windows binaries of xotcl 1.3.5 will be released early next week. Best regards -gustaf neumann

1 0

XOTcl 1.3.5 available
by Gustaf Neumann 15 Jan '05

15 Jan '05

Dear XOTcl Community, Below is the announcement of XOTcl 1.3.5. This is mostly a maintenance and fix release. Besides these fixes, the biggest change makes the non positional argument processing more compliant to the one of OpenACS. One can write now % Object o % o proc foo {-x:boolean -y a b} { ...} instead of % ... % o proc foo {-x:boolean -y} {a b} { ...} Currently, both variants are supported, the latter variant is deprecated and will be removed in the future. This version is also a prerequirement of the soon to be released XOTcl package for OpenACS (integrated with the api and code browser of OpenACS). best regards -gustaf neumann ----- Major changes relative to 1.3.4 are: - Qualitative Improvements * Improved code quality: + fixed possible segmentation violations in non positional argument handling + moved the Serializer into a namespace such that % package req XOTcl % package req xotcl::serializer Serialize .... works without namespace imports (the Serializer is still auto-exported, but this will change in the future) + * Improved Functionality + Non-positional arguments can be used in the same argument list as positional ones (more compliant with OpenACS). One can write now % Object o % o proc foo {-x:boolean -y a b} { ...} instead of % ... % o proc foo {-x:boolean -y} {a b} { ...} All introspection commands will work like before. The old syntax (with the additional argument) is deprecated and will be dropped in the future. + Serializer: support for objects with parent namespaces, which are not xotcl objects + additional instproc for ::xotcl::Class allinstances to return all instances for the actual class

1 0

How to overload Class destroy?
by Zoran Vasiljevic 04 Jan '05

04 Jan '05

Hi! What I want to achieve is to get informed each time a Class is getting destroyed. I do need to know the name of the class and its calling environment (namespace). What I did is: Class create ::xotcl::_destroyer -instproc destroy {args} { puts "DESTROY '[self class]'" puts "DESTROY '[self calledclass]'" puts "DESTROY '[self callingclass]'" next } Class instmixin ::xotcl::_destroyer Now... Class Dummy Dummy destroy ... gives ... DESTROY '::xotcl::_destroyer' DESTROY '::xotcl::Object' DESTROY '' What I expected to get was "DESTROY 'Dummy'" or "DESTROY '::Dummy'" but this does not happen. Why? Thanks, Zoran

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

Xotcl January 2005