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,6413b417b806eb28 X-Google-Attributes: gid103376,public From: jerry@jvdsys.stuyts.nl (Jerry van Dijk) Subject: Re: Accessing C macro constants from Ada95 Date: 1999/04/11 Message-ID: #1/1 X-Deja-AN: 465504105 References: <7eg43i$d3b$1@nnrp1.dejanews.com> <370CC730.4C6112DB@utech.net> <370D7007.2D3AD58B@rocketmail.com> <7el9so$geb@drn.newsguy.com> <7elrg5$egk2@ftp.kvaerner.com> <7emjk8$rp3@drn.newsguy.com> <7ep6uj$o97$1@nnrp1.dejanews.com> <7eqoj2$r27$1@pegasus.csx.cam.ac.uk> Organization: * JerryWare *, Leiden, Holland Newsgroups: comp.lang.ada Date: 1999-04-11T00:00:00+00:00 List-Id: Markus Kuhn (mgk25@cl.cam.ac.uk) wrote: : Calling C library function from Ada95 sucks in one very : significant way: The authors of the C Interface annex of the : Ada95 standard have completely forgotten to generate a facility : for accessing C macro constants. What would be necessary is that every : Ada95 compiler that implements a C interface contains a complete : ISO C macro preprocessor. The question, of course, is: macro constants are only a small portion of the macro's that are defined in header files. What should such a pre-processor do with all the macro functions that can go several levels deep and imbed a lot of function call's ? A tool like c2ada seems to be a much more useful solution. As for constant definition conversion, I usualy do this with a simple editor macro. -- -- Jerry van Dijk | Leiden, Holland -- Team Ada | jdijk@acm.org -- see http://stad.dsl.nl/~jvandyk