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,976a050e0f89277c X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: Urgent question: malloc and ada... Date: 1998/05/02 Message-ID: #1/1 X-Deja-AN: 349593027 References: <352A79C2.15FB7483@nathan.gmd.de> <1998Apr30.180141.1@eisner> <1998May1.104407.1@eisner> X-Complaints-To: usenet@news.nyu.edu X-Trace: news.nyu.edu 894115113 22327 (None) 128.122.140.58 Organization: New York University Newsgroups: comp.lang.ada Date: 1998-05-02T00:00:00+00:00 List-Id: Larry said <> Note here that Larry is agreeing with the proposed criterion for defining the standard C compiler *even* in the case of VMS, which is the one case in which you might have thought that C was not used in the operating system. So, just to recapture the interesting point (I forget who made it). The proposal is that in practice, a working definition of what the standard C compiler means is that it is the C compiler used for wrting the operating system. However, I don't see any analogous way of getting a feel for what the standard Fortran or COBOL compiler may be, and here you definitely need to find out from the vendor which Fortran compiler(s) or COBOL compiler(s) their Ada compiler interfaces to. Of course, as noted elsewhere in this thread, it is perfectly reasonable (and indeed expected) for an Ada compiler to have multiple calling conventions if there are incompatible other-language compilers.