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: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: Compiling, binding, and linking an Ada prog. interfaced with C Date: 1998/08/01 Message-ID: #1/1 X-Deja-AN: 376889164 References: <1998072706002200.CAA02664@ladder01.news.aol.com> <35BD28BF.A5B@atlas.otago.ac.nz> <6pn02g$2ue$1@mulga.cs.mu.OZ.AU> X-Complaints-To: usenet@news.nyu.edu X-Trace: news.nyu.edu 901945779 8880 (None) 128.122.140.58 Organization: New York University Newsgroups: comp.lang.ada Date: 1998-08-01T00:00:00+00:00 List-Id: << > 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. >> Obviously "importing" C macros in full generality would mean inporting the full syntax and semantics of C into the parent language, not something that is remotely feasible at the language definition level if you ask me. Sure a given implementation may be able to rig something up (e.g. if it translates into C anyway).