From:	sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id:	<10212200432.AA05792@clio.rice.edu>
Subject:	More size considerations
To:	djgpp-workers AT delorie DOT com (DJGPP developers)
Date:	Thu, 19 Dec 2002 22:32:38 -0600 (CST)
X-Mailer:	ELM [version 2.5 PL2]
Mime-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com

I've found that dpmiexcp.c uses both write() and _write().  We really only
need _write_int in all of these cases...  but for now I'll at least 
fix the writes to _writes.

What is now _write_int was _write when this was first written; maybe we
should use it in startup code when we need to print messages to stderr.

I'm not sure if extracting _write_int from the same module as _write 
is really needed, since most things will write something, which will
bring in all the other stuff anyway.  But when bad stuff happens and we
want to get a message out, the less stuff we touch the better (and
write and _write currently touch lots of stuff not needed writing to
stderr).

- Raw text -