On Mon, 17 Jul 2006, Rafael Garcia-Suarez wrote: > I come to think that a better idea wrt exit() is one that was proposed > during the referred thread: let exit() exit the application (like > before), and add threads-exit() to exit the thread. Opinions?
I somewhat agree with that because of the backwards compatibility argument. But otherwise I tend to think that exit() terminates the current execution context (which would be just the thread and not the application). It doesn't really matter though as long as there is some other way to terminate the thread from a nested function call without having to return to the main thread function first. So I guess I'm in favor of reverting this change so that the latest threads module can be integrated into 5.8.x as well. Cheers, -Jan
