🚀 go-pugleaf

chris@chrism.demon.co.uk (Chris Marriott) writes:

> In article <1j33gi$6dp@agate.berkeley.edu> jeff@emily10.Berkeley.EDU writes:
> 
> >        I have a question about Windows program execution flow.  I am
> >a little confused so my question may sound confused, but that may
> >not be too bad, because perhaps the form of my confusion will clue
> >you in to what I am confused about...get it?  Probably this question
> >is very naive and that is both because I am a beginner programmer and
> >because I use OWL which hides a lot of the real nuts and bolts of
> >program execution.  (That, I am discovering, has its pluses and minuses)
> >
> >        Lets say I have a function which is dispatched by a Windows
> >message, and that function has some variable X.  Now this function passes th
> >address of X to some other function for processing the contents of X.
> >Let's say I receive the initial Windows message again.  Will the new message
> >dispatch my function, redefining X, and changing the contents of the adress
> >sent to the secondary function before it is done processing it?
> >
> >        Or does a window wait until all processing is finished before
> >handling the next message in its queue?
> >
> 
> Windows 3.x is a *non-pre-emptive* multi-tasking environment.  The processing
> of one message *always* runs to completion before the next message is
> retrieved and processed.
> 
> Chris
> -- 
Close! But no cigar!...  If the code responding to a given message
yields for any reason, it's possible to have your code re-entered
repeatedly.  For instance, a message box thrown up in response 
to a timer message when an error condition is noted will be
called repeatedly until you run out of heap/GDI/stack etc.

- don

------------------------------------------------------------------
Don Hackler  - donh@shakala.com 
Shakala BBS (ClanZen Radio Network) Sunnyvale, CA 408-734-2289