Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!nrl-cmf!ames!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: Contiguous Arrays
Message-ID: <9690@smoke.BRL.MIL>
Date: 23 Feb 89 03:29:13 GMT
References: <2508@ssc-vax.UUCP> <8943@alice.UUCP> <1828@valhalla.ee.rochester.edu> <1989Feb22.171441.7957@utzoo.uucp> <1831@valhalla.ee.rochester.edu>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 9

In article <1831@valhalla.ee.rochester.edu> badri@valhalla.ee.rochester.edu (Badri Lokanathan) writes:
>Yes, accessing the contents of an illegal location
>will almost certainly screw things up, but there is no access happening.

The problem is that even computing the address of an out-of-bounds location
can screw up (and it DOES, on some widespread segmented architectures).
Henry is correct; just because YOU know what the result of such pointer
arithmetic "should" be, does not mean that it will actually turn out that
way at run time.