🚀 go-pugleaf

In <147@autro1.UUCP> teig@autro1.UUCP (Oyvind Teig) writes:
>Event driven systems

>I have always thought of occam as "event driven". A single SEQ
>occam program may be event driven with the external world, but not
>internally. When PARs come into it, isn't occam really VERY
>event driven - even more than MS-Windows programs??

Seems to be a fair point to me. MS windows and other OO systems
are based on asynchronous communications. An event happening does
not require an immediate response, only that the message is queued
for processing. Occam has strong synchronisation in that if a
communication occurs, both parties to the communication implicitly
know when that communictation has occurred. These synchronisation
*events* control the execution flow, and hence drive the exection.

Therefore, I would consider 'event-driven' to be a suitable
term describing the execution of an occam process and by implication
an occam program.

Comments?
	Don


-- 
Don Goodeve|Adaptive Systems|Electronics Dept|University of York
email: don@ohm.york.ac.uk|-------->I speak from my own angle...
 --Disclaimer:--------------------------------------------------
|In the beginning was the word. Man attempted to speak the word |