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 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,3ce5636289df1f84
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2001-08-09 13:29:02 PST
Path: 
 archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!151.189.0.75!newsfeed.germany.net!newsfeed2.easynews.net!easynews.net!news.cid.net!news.enyo.de!news1.enyo.de!not-for-mail
From: Florian Weimer <fw@deneb.enyo.de>
Newsgroups: comp.lang.ada
Subject: Re: pointer in C & in  Ada
Date: Thu, 09 Aug 2001 22:21:38 +0200
Organization: Enyo's not your organization
Message-ID: <87ae19x9v1.fsf@deneb.enyo.de>
References: <86772402.0108071439.1c3e1e40@posting.google.com>
 <otcc7.2752$NJ6.10767@www.newsranger.com>
 <9ksivs$1rs$1@news6.svr.pol.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Xref: archiver1.google.com comp.lang.ada:11705
Date: 2001-08-09T22:21:38+02:00
List-Id: <comp.lang.ada>

"Des Walker" <des.walker@dessy.fsnet.co.uk> writes:

> I didn't read the aforementioned thread, so apologies if this is old
> information. Just for interest on interfacing to C functions, I note
> that the C-FAQ mentions some platforms that use different addressing
> mechanisms depending on the type of object being addressed, in a
> discussion about the null pointer in C.
>
> http://www.eskimo.com/~scs/C-faq/q5.17.html

| The old HP 3000 series uses a different addressing scheme for byte
| addresses than for word addresses; like several of the machines above
| it therefore uses different representations for char * and void *
| pointers than for other pointers.

So even on this architecture, HP got the char * <-> void *
correspondence right, it seems.  Most probably, there is really
nothing to worry about.