Message-Id:	<3.0.5.16.19980827202740.2cfff282@mail.tir.com>
Date:	Thu, 27 Aug 1998 20:27:40 -0400
To:	djgpp AT delorie DOT com
From:	"Thomas J. Hruska" <thruska AT tir DOT com>
Subject:	Re: Display question...
In-Reply-To:	<Pine.SUN.3.91.980827144745.6326h-100000@is>
References:	<35E4E7EF DOT CF07B3F4 AT post DOT comstar DOT ru>
Mime-Version:	1.0

At 02:49 PM 8/27/98 +0300, Eli Zaretskii wrote:
>On Thu, 27 Aug 1998, Dim Zegebart wrote:
>
>> Since DJGPP has UNIX ancestor it has some UNIX features too. So, in UNIXall
>> streams (stdout is a stream) are buffered and behave exactly as you
describe.
>
>The real reason for this buffering is performance: every write needs a 
>switch from protected to real mode and back.  So writing every character 
>with a separate call to DOS will severely punish programs that print 
>large amounts of text to the screen.

I'm writing a spreadsheet block converter in Borland Turbo C (16-bit) which
I will compile under DJGPP once I've got it working.  DJGPP has poor
error/warning alerts compared to Borland's (I use the IDE in both cases).
How badly is the performance cut since I only want to let the user know
that the program is working and to please wait?  Since most of the activity
of the program is hard drive related (and some blocks can take 5-10 seconds
to process in a 16-bit environment), I figured 32-bit was the best way to
go to speed things up a bit.

How long does it take to switch to and from real mode?


                 Thomas J. Hruska -- thruska AT tir DOT com
Shining Light Productions -- "Meeting the needs of fellow programmers"
         http://www.geocities.com/SiliconValley/Heights/8504
                    http://shinelight.home.ml.org

- Raw text -