Date: Wed, 28 Aug 1996 08:09:37 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: DJ Delorie <dj AT delorie DOT com>
Cc: djgpp-workers AT delorie DOT com
Subject: Re: getc and putc: not macros
In-Reply-To: <199608271200.IAA19710@delorie.com>
Message-Id: <Pine.SUN.3.91.960828080426.13692A-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Tue, 27 Aug 1996, DJ Delorie wrote:

> In theory any function can be "inlined" (if gcc permits), but each
> time you do so you make it so that you have to recompile sources to
> upgrade libc.  With all the work we've been doing on text vs binary, I
> didn't feel like recompiling all the gnu utilities instead of just
> linking.

That is only a consideration if you keep all the .o files in between libc 
changes.  Such a situation is perhaps common during alpha/beta testing, 
but not otherwise (at least the way I manage my disks).  Usually, it's 
much less hassle to just unzip the sources and rebuild everything.  And 
even if .o are present, you can always `make clean' and rebuild: doesn't 
take too much for most packages.

Anyway, if the gain from using a macro or an inline function is minimal, 
then doing it isn't worth the hassle either.  I just wanted to be sure 
this isn't something that just slipped us by chance.