Subj : Re: What would an event-driven/threaded programming language have?
To   : comp.programming.threads
From : Ronald Landheer-Cieslak
Date : Tue Mar 22 2005 02:03 pm

cvrebert@gmail.com wrote:
> I am a Python/C programmer with no threaded/event-driven programming
> experience. I would like to know what language constructs would be
> useful for threaded/event-driven programming. That is, if someone were
> to design a language specifically for event-driven/threaded
> programming, what features would it have? Pseudo-code for this
> hypothettical anguage would be helpful. Either curly-brackets family
> (C*/Java-ish) or Python-like code would be best. My goal would be to
> reduce design patterns/idioms to mere language features.
> Thank you for your time and input.
First: threading and event driven programming is not the same thing. For
threading, you'd need to clearly define what is thread-safe, how
thread-safe it is, what threads are, how to synchronize them, etc.

For event-driven programming, you'd look more into finite state machines
and things like that: how to define the states of a machine, how to
define valid state changes and what to do when the state does change, etc.

Event-driven programs may be inherently threaded, but might not be: it
all depends on how you handle the events (whether there's a scheduler
that simply "trigs" a machine when an event occurs or whether no two
events can occur at the same time.

HTH

rlc

.