🚀 go-pugleaf

James: thanks for the reply. Guess it's time to get my own copy of Core
Java, instead of borrowing one from a colleague.

>>By posting, but keeping the current thread
running, you are really crossing your fingers and hoping that the
current
thread keeps its time slice.  But the reality is that once the message
gets
posted, the block is removed from the receiver of the post.  So we may
or
may not get the intended action.  The os may decide to keep the current
thread running, or may switch to the other.<<

I see your point. That wasn't a problem in Win16 because there was no
such thing as multi-threading. Is it possible to build a Java app that
does not multi-thread? I mean, if I avoid starting new threads myself,
and post events to the queue, will the OS still (potentially) break away
from my code block and deliver the event to its target before my code
block is finished?

I'm trying to write a conversion tool from SQLWindows to Java. One way I
could do it is to write single-threaded apps, use posting, then explain
to developers how to (1)make the apps multi-threaded and (2) stop
posting at the same time, with manual edits.

Regards,
Mark Hunter