On Thu, 18 Jan 2001, Kristoffer Lawson wrote:
Yes, this is exactly why explaining, and even reproducing the problem is difficult. In any case, I do believe we probably have found a bug, as a method is being run and while it is run at some point it gets a message that [self] called after destroy, or something like that. Thus we've had to work around this in a rather complex fashion. I'll try to explain it as best I can:
Found the problem:
On the machine the guy is running, the version of XOTcl is 0.81, which bugs in the case described. He's now upgrading...
Doh.
- ---------- = = ---------//--+ | / Kristoffer Lawson | www.fishpool.fi|.com +-> | setok@fishpool.com | - - --+------ |-- Fishpool Creations Ltd - / | +-------- = - - - = --------- /~setok/