-=> /* Quoting Jeff Guerdat to Frank Sexton */ <=-
 FS> This is good multi-threading.
 JG> This has been in Procomm Plus for windows since at
 JG> least v2.0 (it may have been 1.0 but I can't remember
 JG> that far back).  This is a 16 bit app.
The way I understand it, although a system may be able to
multi-task multiple 16-bit apps, the 16-bit apps themselves
cannot contain separate multiple threads like 32-bit apps
can.  A 16-bit app can "simulate" similar operation as
threads, but can't come close in performance, functionality
and efficiency.
 FS> I'd like to see NT, it's apps, and other operating
 FS> systems and apps get serious about multi-threading.
 FS> Multi-threading is NOT just for "heavy-hitting"
 FS> applications.  Just the opposite in fact, as far as
 FS> I'm concerned.
 JG> Agreed.  Smoothness of operation counts for as much as
 JG> raw power...
Another point I like to make is one to contradict often
heard phrases such as "only power users would ever need
that".  I believe, if fact, that the primary benefit of a
powerful multi-tasking and multi-threading operating system
is to specifically AVOID the need for the user to be a
knowledgeable "power" user.  The operating system with full
utilization of it's potential by programmers is exactly
what makes it *easy* to use.
Bottom line, I wish many programmers would take much more
advantage of their selected multi-tasking multi-threaded
operating system of choice.  There's far too many DOS
"ports".  They're just not in the same league as apps where
it is apparent that the programmer is fully utilizing the
"system" capabilities.
-Frank
(fsexton@xpert.net - http://www.concentric.net/~fsexton)
--- Blue Wave/OS2 v2.30
---------------