From: "Gregg N" 


"Geo"  wrote in message news:417c570f{at}w3.nls.net...
> "Paul Ranson"  wrote in message
> news:417bd171$1{at}w3.nls.net...
>
> > If you look at the assembly language output from your C++ compiler
you'll
> > see that your entire program is devoted to printing two pre-calculated
> > constants.
>
> 193K executable?
>
> Let me put this in perspective. When I used to do things in assembler, the
> disk size was 128K, this program would not even have fit on a single sided
> Apple }{ floppy disk.
>
> So what's the other 192K, a life support system?
>
> Geo.

The more useful test is how much additional space is taken up incrementally
as you add new code. The baseline size doesn't tell you much except that
the I/O facility takes about 190k. This is not a function so much of the
language as it is of the granularity of the library that gets linked in.

When I compiled your sample with /MD the executable was only 3,584 bytes.
This tells the compiler not to statically link the runtime library, but to
use msvcrt dll instead. I also specified /O1 which is optimize for size.

Gregg

--- BBBS/NT v4.01 Flag-5