Sender: nate AT cartsys DOT com
Message-ID: <35E733E7.BE5A1DB7@cartsys.com>
Date: Fri, 28 Aug 1998 15:49:11 -0700
From: Nate Eldredge <nate AT cartsys DOT com>
MIME-Version: 1.0
To: Endlisnis <s257m AT unb DOT ca>
CC: djgpp AT delorie DOT com
Subject: Re: Display question...
References: <35E4E7EF DOT CF07B3F4 AT post DOT comstar DOT ru> <3 DOT 0 DOT 5 DOT 16 DOT 19980827202740 DOT 2cfff282 AT mail DOT tir DOT com> <35E6BBBB DOT E534153 AT unb DOT ca>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

Endlisnis wrote:
> 
> Thomas J. Hruska wrote:
> > I'm writing a spreadsheet block converter in Borland Turbo C (16-bit) which
> > I will compile under DJGPP once I've got it working.  DJGPP has poor
> > error/warning alerts compared to Borland's (I use the IDE in both cases).
>         Options->Compilers->Warnings->Wall
> That will make GCC as good or better at detecting bad-code.

It detects it quite well, but doesn't always explain it well.  I once
had a bug involving a missing parenthesis in a complicated macro.  GCC
just said "Parse error", which didn't help me much.  In desperation I
submitted the code to Turbo C, got a "Missing )" message, and had it
fixed quickly.  But that is less important.
-- 

Nate Eldredge
nate AT cartsys DOT com