Re^2: code executed at end of a thread

That's so far my best guess too - except that my design is that I'm writing a generic library, and don't have a control over what threads do, that's up to the programmers. I'd hate to impose an extra requirement, like "hey use my lib but also use a goto" (I personally don't mind goto at all, and use them too), but you get my drift...

I thought rather that I missed some obscure language feature, and am trying to reinvent a wheel.

Comment on Re^2: code executed at end of a thread

Replies are listed 'Best First'.
Re^3: code executed at end of a thread by zentara (Cardinal) on Dec 04, 2009 at 18:22 UTC
.... well then, use the nested labeled loops, as i suggested..... that code is just a simple example to illustrate exacting thread control..... running threads on manual so to speak, rather than requireing a thread helper library like a queue......and goto's are such a clean hack, that everyone should have it in their toolkits, even if the bossman dosn't like them :-) ....you can start up threads and pass perl code strings to them, thru shared variables, and have them eval'd in the thread.....but then the ugliness of an exit call taking down the whole house of cards raises it's head..... i don't know what you are doing, but threads may not be what you are looking for....unless you are on win32..... bwahaha.... then i can't help ....but you may have a bigger design problem with module safety..... hows that for bllsht ;-) I'm not really a human, but I play one on earth. Old Perl Programmer Haiku	[reply]
Re^4: code executed at end of a thread by dk (Chaplain) on Dec 05, 2009 at 13:22 UTC
"unless i'm on 32"... year right :) I'm using threads to emulate a proper popen() on win32 that returns a handle that I can use in select() . Other than this, the advice above with END inside eval actually works for me just fine. thanks for a brainstorm!	[reply]