Date: Sun, 20 Jul 2003 11:29:30 +0200
From: "Eli Zaretskii" <eliz AT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: djgpp AT delorie DOT com
Message-Id: <3405-Sun20Jul2003112929+0300-eliz@elta.co.il>
X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
In-reply-to: <i7dkhvssmdlj1cgd4ciiog3pusnupjd1fk@4ax.com> (message from
	RadSurfer on Sun, 20 Jul 2003 02:29:54 -0400)
Subject: Re: (3) HELP Please with C++
References:  <i7dkhvssmdlj1cgd4ciiog3pusnupjd1fk AT 4ax DOT com>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: RadSurfer <RadSurfer AT yahoo DOT com>
> Newsgroups: comp.os.msdos.djgpp
> Date: Sun, 20 Jul 2003 02:29:54 -0400
> 
> Why is the C++ executable  507,145 bytes???
> 
> yikes!
> 
> More discussion please....
> How does one get the EXE size down to something practical?

By reading the FAQ, of course (section 8.14).

> BTW: A nearly similar Borland BCC32 compile of HW.CPP
>   results in 
> .....A 07-20-2003 01:42        100   5357307D HW.CPP
> .....A 07-20-2003 01:42       4958   95E194DE HW.obj
> .....A 07-20-2003 01:42     143360   53C13363 HW.exe
> 
> 1/5th the EXE size of the DJGPP !!

I'm guessing that BCC32 supports a subset of ANSI C++ and that its
.exe file is stripped of debugging info.  Again, see the FAQ for more
about this.