Lex Spoon wrote:

> Maybe continuations would help.  An event handler *could* be allowed to stop at any arbitrary point to wait for another event.  (This could be implemented using suspended Processes).  It would certainly make the event handlers simpler, because they could go back to using regular old loops.  But then, how do you arrange for the suspended handlers to be given the events they need?  And how do you keep from having all these suspended handlers around that might never in fact get woken back up (eg, their window closed)?
>

Take a look at "Escaping the event loop: an alternative control
structure for multi-threaded GUIs" by Matthew Fuchs
    http://cs.nyu.edu/phd_students/fuchs/
in which he applies a general continuation passing style to event driven
GUI programming.

> Has anyone here ever worked in such a system?  (And, is Squeak bound to touch on every single OS and programming language issue that has come up in the last 20+ years, as it goes along?  :))

Yes, and every single educational, human-computer interface, usability,
AI/alife, concurrency, mathematical, ... issue ever vaguely associated
with computers, and a number that nobody has thought of yet. ;-)

-- Dwight