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,95d036084078aa89 X-Google-Attributes: gid103376,public From: eachus@spectre.mitre.org (Robert I. Eachus) Subject: Re: Compiling, binding, and linking an Ada prog. interfaced with C Date: 1998/07/30 Message-ID: #1/1 X-Deja-AN: 376416600 References: <1998072706002200.CAA02664@ladder01.news.aol.com> <35BD28BF.A5B@atlas.otago.ac.nz> <6pn02g$2ue$1@mulga.cs.mu.OZ.AU> Organization: The Mitre Corp., Bedford, MA. Newsgroups: comp.lang.ada Date: 1998-07-30T00:00:00+00:00 List-Id: In article <6pn02g$2ue$1@mulga.cs.mu.OZ.AU> fjh@cs.mu.oz.au (Fergus Henderson) writes: > This is one respect in which Ada's otherwise excellent C interface > features are not quite as good as those of Mercury or ISE Eiffel, > which both allow you to import C macros without having to write a > separate C file containing glue code. Huh? The Ada way to imitate C in this area is to run the C preprocessor over your code and live with the result no matter how bizarre, just like it works in C. Of course, if you have C macros that actually generate C source, then you can only use those inside units written in C. Several Ada compilers come with C style preprocessors as well. But not many people use them. Ada programmers don't like obfusticated code, and the preprocessor is the easiest way to obfusticate things. -- Robert I. Eachus with Standard_Disclaimer; use Standard_Disclaimer; function Message (Text: in Clever_Ideas) return Better_Ideas is...