From: Mike '/m' 

On Sun, 8 May 2005 22:06:35 -0400, "Geo"  wrote:

>"Tony Ingenoso"  wrote in message
>news:427eb908$1{at}w3.nls.net...
>
>> Don't laugh, I've seen an editor (one of Borland's first OS/2 apps) under
>> the OS/2 kernel debugger that allocated and freed a 1 byte segment on
>every
>> keystroke.  Every keystroke was two expensive trips through kernel memory
>> management.  Programmers do some pretty dumb things...
>
>this I can believe, I remember some borland dos app that used to run NT to
>100% cpu usage because of it's key poling routine and as a programmer I've
>done some pretty dumb things so I have no problem believing that either.
>
>But there are other issues. Most of the apps that I use don't have a problem
>with cpu speed being the bottleneck, the times I spend waiting for the app
>are usually when it's talking to the disk or network.

In a previous life, I used Greenleaf's Comm library for some comm file
transfer programs I wrote.  I polled the Esc key to see if the user wanted
to break out of the comm program.

When I switched the host of the program to OS/2 (to allow multiple
instances of it to run using multiple comm ports), the performance was
awful due to the polling.  Then I stuck a call to the DOS interrupt to
"yield the CPU" in the polling loop.

All was wonderful after that.

 /m

--- BBBS/NT v4.01 Flag-5