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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,2adc22b0e703907e X-Google-Attributes: gid103376,public From: tmoran@bix.com Subject: Re: Representation question (void *) Date: 1999/11/17 Message-ID: #1/1 X-Deja-AN: 549616530 References: X-Complaints-To: abuse@pacbell.net X-Trace: typhoon-sf.snfc21.pbi.net 942826709 206.170.24.51 (Wed, 17 Nov 1999 00:18:29 PST) Organization: SBC Internet Services NNTP-Posting-Date: Wed, 17 Nov 1999 00:18:29 PST Newsgroups: comp.lang.ada Date: 1999-11-17T00:00:00+00:00 List-Id: >The closest semantic equivalent to C's void* is Ada's System.Address. >This is *almost* certain to be compatible (I doubt that there's an >existing system on which they're different), but the language doesn't >guarantee it. I'm looking at an Ada 95 compiler manual that says its Ada "Access a_type" maps to "*a_type". It also says: "System.Address for Windows NT compilers is 48 bits, including the segment. Most 32 bit C compilers cannot use the segment information. If your compiler can, the declaration would likely be 'far *a_type'. Otherwise ... pass the (offset component) as '*a_type'. That will work only if the address has the same segment as your program." We've found in CLAW, which of course is in the business of talking to C (Windows), a rather modest need for "void". A quick scan shows 63 SLOC containing the words Void or LPVoid, out of about 125 KSLOC. YMMV