From: elf AT netcom DOT com (Marc Singer)
Message-Id: <199610251922.MAA24440@netcom3.netcom.com>
Subject: Re: DJGPP V2.01 Released
To: alaric AT abwillms DOT demon DOT co DOT uk (Alaric B. Williams)
Date: Fri, 25 Oct 1996 12:22:56 -0700 (PDT)
Cc: djgpp AT delorie DOT com (DJGPP List Alias)
In-Reply-To: <846263987.18931.0@abwillms.demon.co.uk> from "Alaric B. Williams" at Oct 24, 96 06:43:28 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 612       

> > Did anybody thougt about including the 
> > 
> >   'Bounds Checking for C' 
> >   (see http://www-ala.doc.ic.ac.uk/~phjk/BoundsChecking.html)
>  
> > option in a DJGPP build compiler? Most time I just turn around and
> > around
> > to find those little stupid errors accessing arrays, dynamic chains, ...
> 
> Hmmm, anybody have any opinions?

What does this option do?  AFAIK there is no compile-time check for
bounds that is possible in C.  If it is a runtime check, then I'm very
much against it.  There are utilities to help programmers find memory
leaks and they are best left optional.

-- Marc Singer