From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Thread: 103376,7b65fc33a05f24b6
X-Google-Attributes: gid103376,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news2.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!nx02.iad.newshosting.com!newshosting.com!69.16.185.11.MISMATCH!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post01.iad.highwinds-media.com!newsfe03.iad.POSTED!4a71828c!not-for-mail
From: Hyman Rosen <hyrosen@mail.com>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: A curiosity...
References: 
 <a88dafcc-04d0-4a46-a168-7cb034894181@k41g2000yqn.googlegroups.com>
 	<d49568ae-d205-457f-bf10-61e08b23b858@t26g2000prh.googlegroups.com>
 	<ffYZk.17574$st1.15396@newsfe10.iad>
 <0f009ce8-0f50-4b85-9368-0d0c68f42da1@w34g2000yqm.googlegroups.com>
 <396044ea-4c37-4923-b989-eb4af2202bd3@o2g2000yqd.googlegroups.com>
In-Reply-To: 
 <396044ea-4c37-4923-b989-eb4af2202bd3@o2g2000yqd.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <4MYZk.14365$M33.3189@newsfe03.iad>
X-Complaints-To: abuse@WWWSpace.NET
NNTP-Posting-Date: Thu, 04 Dec 2008 22:24:00 UTC
Date: Thu, 04 Dec 2008 17:24:00 -0500
Xref: g2news2.google.com comp.lang.ada:3851
Date: 2008-12-04T17:24:00-05:00
List-Id: <comp.lang.ada>

Ludovic Brenta wrote:
> And I think this rule is responsible for the "limitation" that all
> current processor architectures use addresses which are the same size
> as integers. Before the advent of C, address size and word size were
> not necessarily the same; now they always are, and that's *only* for
> compatibility with C.

No such limitation exists. In fact, for many years C compilers on the
Intel x86 architecture used 16-bit integers and 32-bit pointers.

> map extremely well to Ada's storage pools and very poorly with C's
 > pointer arithmetic.

C's pointer arithmetic exists only within the confines of a single
array. Unless your Ada storage pools are planning to allocate single
objects with memory spanning separate devices, C's pointer arithmetic
model will be just fine.