On 7 Apr 2008, at 11:15 pm, Hans Bulfone wrote:
and i'd find it even better if we could change the behaviour of the default exception handler to unwind the dynamic-wind stack before exiting or terminating the thread. i think it's a more useful default behaviour... but i don't know if it's easily doable...
Can it not be done by wrapping every thread (even the primordial one) in a conventional exception catching block, which then generates a normal exception handler which calls to a continuation up in the dynamic scope of the catching block, thus unwinding the stack? Then it can just catch the exception and report exceptional thread termination, or in the normal course of events cleanly shut the thread down. Should be an easy fix, no?
just my 2 cents... hans.
ABS -- Alaric Snell-Pym Work: http://www.snell-systems.co.uk/ Play: http://www.snell-pym.org.uk/alaric/ Blog: http://www.snell-pym.org.uk/?author=4 _______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
