Karl Lattimer wrote: > If the engine is informed (signaled) of events then it would go from > event occurs, *run in circles* what do i do, what DO i do, oh thats what > i do, bish bash bosh event handler execs. > > I see a GUI rendering thread, an event thread and a GUI event handler > thread running concurrently. > > How does python handle threading? (superbly i assume)
No threads please. The problem with threads is not Python, it is the
programmer. You need to take care of many things that will go wrong
for some users who can't reproduce the bug and you will never see it
at all: maybe some locks are missing and we access a variable from two
threads with bad site effects. Or we use a lock and create stuff like
deadlocks, livelocks (e.g. after-you-after-you) or starvation. Should
I go one? I could complain about threads all day long. :)
now, where is that signature ... ah, there it is.
Dischi
--
"A Computer is a state machine.
Threads are for people who can't program state machines."
- Alan Cox
pgpiCQ2icJvmp.pgp
Description: PGP signature
