[Xotcl] Catching errors in calls to "next"
Gustaf Neumann
neumann at wu-wien.ac.at
Tue Nov 16 00:44:26 CET 2004
On Monday 15 November 2004 18:51, MichaelL at frogware.com wrote:
> Ok, I've found a temporary workaround using
>
> TestB create ::b -x 5
>
> rather than
>
> TestB ::b -x 5
>
> Still, why doesn't the second approach work?
XOTcl used XOTCL_UNKNOWN to flag the situation, where
a filter catches an unknown call, such that the dispatcher
knows when to call "unknown" in the presence of filters.
i have changed the internal communication from the tcl
return code to an internal flag. XOTCL_UNKNOWN is
gone, both of the above examples do work now (i.e.
will work in the forthcoming version).
With Zoran's help with the wonderful purify, i fixed over the
weekend an old bug showing up in the new extended regression
test (access to freed memory), so the biggest blocker of
the new release is gone. we should check, how to deal
with the recent glitches showing up here...
-gustaf
--
Univ.Prof. Dr.Gustaf Neumann
Abteilung für Wirtschaftsinformatik und Neue Medien
Wirtschaftsuniversität Wien, Augasse 2-6, 1090 Wien
More information about the Xotcl
mailing list