Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!ucsd!ucbvax!tut.cis.ohio-state.edu!sei.cmu.edu!firth From: firth@sei.cmu.edu (Robert Firth) Newsgroups: comp.arch Subject: Re: Segmented Architectures ( formerly Re: 48-bit computers) Message-ID: <23658@as0c.sei.cmu.edu> Date: 4 Apr 91 22:14:00 GMT References: <1991Apr04.023845.3501@kithrup.COM> <23615@as0c.sei.cmu.edu> <4919@lib.tmc.edu> Reply-To: firth@sei.cmu.edu (Robert Firth) Organization: Software Engineering Institute, Pittsburgh, PA Lines: 17 In article <4919@lib.tmc.edu> jmaynard@thesis1.med.uth.tmc.edu (Jay Maynard) writes: >Survey says: Bzzt! > >There's nothing that says that array elements in FORTRAN - or, for that >matter, C - have to be contiguous. Thinking that that must be true as a >matter of Natural Law is purest VAXocentrism. I suggest you check ANSI X3.9-1978, especially sections 5.2.5 and 5.4.3. The standard requires that an array be associated with a "storage sequence" in column-major form, and that there be a one to one mapping between the "subscript values" and the elements of this storage sequence. Naturally, these elements need not be contiguous in physical storage, which isn't what I asked for, since I explicitly referred to virtual memory. But they do have to be contiguous in the virtual memory model of the Fortran language. I await your suggested implementation.