Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!odi!dlw
From: dlw@odi.com (Dan Weinreb)
Newsgroups: comp.object
Subject: Re: Type-safe does not mean safe
Message-ID: <1990Oct11.063340.11414@odi.com>
Date: 11 Oct 90 06:33:40 GMT
References: <3832@osc.COM> <1990Oct2.170910.4805@eua.ericsson.se>  
 <CLINE.90Oct4111329@cheetah.ece.clarkson.edu> <1990Oct5.010703.16019@Neon.Stanford.EDU> <1990Oct5.184609.7942@odi.com> <18260.27130e32@qut.edu.au>
Reply-To: dlw@odi.com
Organization: Object Design, Inc.
Lines: 6
In-Reply-To: rnews@qut.edu.au's message of 10 Oct 90 12:04:02 GMT

Yes, you are quite right; I acknowledge that I overstated my case.
There are certainly compilers for Pascal, FORTRAN, and PL/I that
generate array-bounds-checking code, sometimes optionally (and
sometimes by default and sometimes not).  I got carried away from
excessive recent exposure to conventional implementations of C and C++
in which such checking is not available.