Hello Bill!
> > ... Nonetheless I find it surprising that there is no chance
> > within thread A to kill thread B.
>
> I'm not surprised, as threads are supposed to be independent of
> each other...
> ...that's one of the main reason for having threads.
>
> If there is (?) a way, I would assume that it could ONLY be
> done in or by a parent.
Ah, and I thought, object oriented programming is to model reality
where killing siblings is not too rare, at least in history.
May be you are right as for computing anarchy is not adequate,
here only the parents may kill their own offspring.
But when I look at 'ooRexx Reference Version 4.1.2' chapter 1.4
'How Objects Interact' I may imagine one object running thread A
to send a message to an other object running thread B with the
contents: "Perish!" or "Quick Quit" or something similar, but this
are just ideas ("Who has visions shall go to the doctor.") So I
must re-read Mark's investigations before i fantasise. ;)
Best,
M.
--------------------------------------------
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: www.ok.de
------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
