From:	"Ian Miller" <Ian AT shelob DOT plus DOT com>
Newsgroups:	comp.os.msdos.djgpp
References:	<madoka-6C398A DOT 16411011112000 AT news DOT supernews DOT com>
Subject:	Re: DJGPP and Borland's compiler generated code size
Lines:	28
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
Message-ID:	<tBvP5.512$I5.3440@stones>
Date:	Sun, 12 Nov 2000 11:58:45 -0000
NNTP-Posting-Host:	212.159.59.123
X-Complaints-To:	abuse AT plus DOT net DOT uk
X-Trace:	stones 974030297 212.159.59.123 (Sun, 12 Nov 2000 11:58:17 GMT)
NNTP-Posting-Date:	Sun, 12 Nov 2000 11:58:17 GMT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

"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.

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.

Ian

- Raw text -