From: Nate Eldredge <neldredge AT hmc DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: DJGPP and Borland's compiler generated code size
Date: 12 Nov 2000 09:36:14 -0800
Organization: InterWorld Communications
Lines: 36
Sender: nate AT mercury DOT st DOT hmc DOT edu
Message-ID: <83puk1gkj5.fsf@mercury.st.hmc.edu>
References: <madoka-6C398A DOT 16411011112000 AT news DOT supernews DOT com> <tBvP5.512$I5 DOT 3440 AT stones>
NNTP-Posting-Host: mercury.st.hmc.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: nntp1.interworld.net 974050576 56163 134.173.57.219 (12 Nov 2000 17:36:16 GMT)
X-Complaints-To: usenet AT news DOT interworld DOT net
NNTP-Posting-Date: Sun, 12 Nov 2000 17:36:16 +0000 (UTC)
User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.5
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

"Ian Miller" <Ian AT shelob DOT plus DOT com> writes:

> "Julian Hsiao" <madoka AT novastar DOT com> wrote in message
> news:madoka-6C398A DOT 16411011112000 AT news DOT supernews DOT com...
> > Hi,
> >
> > I'm currently taking a programming class and being short on budget, uses
> > DJGPP and Borland's free compiler...  The
> > reason I use both compilers is because I try to avoid using certain
> > constructs that only GCC or Borland provides (well, I guess the only way
> > to completely avoid that is to code while reading the C++ specs paper,
> > but I'll pass on that...).
> 
> I do it by consulting my copy of Bjarne Stroustrup's
> book "The C++ Programming Langauge" rather than
> rely on on-line help systems which never draw the
> distinction between standard and extended features.
> Once one is reasonably familiar with the language
> this is not particularly arduous.

In gcc, all their non-standard extensions are supposedly listed in an
"Extensions" section of the manual.  Furthermore, there is a switch
which will warn you if you use any of them.  -ansi or -pedantic, I
forget which is which.

> Compiling a piece of code on several different
> compilers is a marvelous stress test, however.  In
> my experience it almost always turns up a subtle
> bug or two.

Won't argue there.

-- 

Nate Eldredge
neldredge AT hmc DOT edu