> The leaving() method is a good place to do clean up. It is not correct to
> say you "have" to add the method. You could code your clean up in the ok()
> or cancel() also.
The more choices I have the more information I need to make the
> I think your logic is a little faulty here. Just because you can
> externally kill a Rexx program does not necessarily mean you *must* be able
> to kill it from within the program.
Darned! That woud be a nice one: in addition to normal EXIT
something like a "hard exit", that just 'pulls the plug'. But as
ooREXX may be used as scripting language I may trigger a re-IPL -
or how do you say on Windoz - 'shut down and boot again' :)
> I don't know of any way to do that. You need to figure out a way to signal
> the thread to quit. I suggested 2 ways you might be able to signal the
> thread to quit. I don't know of any other ways myself.
> 1.) ...
> 2.) ...
You are very patient with beginners. SockClose(h) with the correct
'h' ends a socket, even in blocking mode. It was just the correct
'h' what tangled me. Sorry! ;)
Nonetheless I find it surprising that there is no chance within
thread A to kill thread B.
Kostenlose E-Mail-Adresse mit unbegrenztem Speicherplatz für E-Mails, Free SMS und OK-Drive, der Online-Festplatte.
Sicher Dir jetzt Deine Wunschadresse @ OK.de: http://www.ok.de