X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Message-ID: <3C82C4F7.20E7F821@yahoo.com>
Date: Sun, 03 Mar 2002 19:51:03 -0500
From: CBFalconer <cbfalconer AT yahoo DOT com>
Organization: Ched Research
X-Mailer: Mozilla 4.75 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: Malloc/free DJGPP code
References: <10203021522 DOT AA15526 AT clio DOT rice DOT edu> <3C8118C3 DOT C4EF9685 AT yahoo DOT com> <4331-Sat02Mar2002220420+0200-eliz AT is DOT elta DOT co DOT il>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Eli Zaretskii wrote:
> 
... snip ...
> 
> Why do you think so?  The call to _write is already in startup code,
> so you won't be bloating the code too much.
> 
> > I assume write to the stderr handle will work as well as write to
> > the stdout handle (not fwrite to streams).

I am getting debug access to things to allow diagnostic software
to interface cleanly, and I am finding anamolies between fwrites
(from the application) to stdout (the stream), and writes to
STDOUT (the handle) from the internal debugging code.  Causes
great confusion. I would much prefer things to appear in the order
written :-)

Even though the fwrites (or printfs etc) have \n terminators, the
only way I have found to get it out on the screen before the later
handle writes is to use an extra fflush.

Are there any known rules for this sort of stuff?

-- 
Chuck F (cbfalconer AT yahoo DOT com) (cbfalconer AT XXXXworldnet DOT att DOT net)
   Available for consulting/temporary embedded and systems.
   (Remove "XXXX" from reply address. yahoo works unmodified)
   mailto:uce AT ftc DOT gov  (for spambots to harvest)