From: Paul Shirley <Paul AT no DOT spam DOT please>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Hello world!
Date: Mon, 5 Jan 1998 15:37:59 +0000
Organization: wot? me?
Distribution: world
Message-ID: <35C3$HAX5Ps0Ewda@foobar.co.uk>
References: <34B0250F DOT 4E7 AT netspace DOT net DOT au> <34B05477 DOT 4DEF AT nic DOT smsu DOT edu>
 <34B05EEB DOT FB68C746 AT bethany DOT edu> <34B07279 DOT 1B31 AT nic DOT smsu DOT edu>
Reply-To: Paul Shirley <Paul AT chocolat DOT obvious DOT fake DOT foobar DOT co DOT uk>
NNTP-Posting-Host: chocolat.foobar.co.uk
Mime-Version: 1.0
Lines: 19
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

In article <34B07279 DOT 1B31 AT nic DOT smsu DOT edu>, Tony O'Bryan
<aho450s AT nic DOT smsu DOT edu> writes
>> Which is more of a C++ version as taught in the books. It compiles
>> signifigantly larger (I didn't strip it though).
>
>Using the iostreams links in another library (libgpp.a) which naturally
>will increase the size of the final program.  Libraries aside, the code
>produced by a C++ compiler shouldn't be much larger (if at all) than the
>same code produced by a C compiler, though optimization options will
>have an effect.

Its partly because the iostreams library has so many internal linkages
that you get all of it linked if you use any of it. Its a one-off cost,
annoying but it also happened with the commercial compilers I've used.

If its a big problem use C io functions instead.

---
Paul Shirley: my email address is 'obvious'ly anti-spammed