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,1e82cb45ab839370,start X-Google-Attributes: gid103376,public From: Florian Weimer Subject: Interfaces.C and void * Date: 1999/09/22 Message-ID: <87btavxw93.fsf@deneb.cygnus.argh.org>#1/1 X-Deja-AN: 528143631 Mail-Copies-To: never Content-Type: text/plain; charset=us-ascii X-Complaints-To: abuse@cygnus.argh.org X-Trace: deneb.cygnus.argh.org 937983864 4482 192.168.1.2 (22 Sep 1999 07:04:24 GMT) Organization: Penguin on board Mime-Version: 1.0 User-Agent: Gnus/5.070096 (Pterodactyl Gnus v0.96) Emacs/20.4 NNTP-Posting-Date: 22 Sep 1999 07:04:24 GMT Newsgroups: comp.lang.ada Date: 1999-09-22T07:04:24+00:00 List-Id: Recently, I wrote a binding for a C library which provides an abstract data type and completely hides the underlying representation of the type (i.e., all the public routines work on pointers to void). Is there really no portable equivalent of a C void * in Interfaces.C? I used Interfaces.C.Strings.chars_ptr, which should be quite portable in practice, but AFAIK, ISO C doesn't require the representation of void * and char * to be identical.