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=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,ff4487ffe32cc5a4 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1994-09-24 14:14:02 PST Newsgroups: comp.lang.ada Path: bga.com!news.sprintlink.net!howland.reston.ans.net!noc.near.net!inmet!dsd!bobduff From: bobduff@dsd.camb.inmet.com (Bob Duff) Subject: Re: Package Interface, and interoperbility Message-ID: Sender: news@inmet.camb.inmet.com Organization: Intermetrics, Inc. References: Distribution: comp Date: Sat, 24 Sep 1994 21:05:53 GMT Date: 1994-09-24T21:05:53+00:00 List-Id: In article , wrote: >I have been studying the package Interface and I am puzzled about how >Ada implementations will be able to interface with other languages in >one specific situation. I'm probably overlooking some important feature >so I hope somebody will enlighten me. The idea is that implementations will provide various interfaces specific to particular implementations (if necessary), such as Interfaces.Microsoft_C, Interfaces.Borland_C, Interfaces.Some_Other_C. Interfaces.C will just be an interface to the "default" C compiler: package Interfaces.C renames Interfaces.Whatever_C; If you don't like the default, compile a different renames, or else directly 'with' Interfaces.Your_Favorite_C. In practice, most C compilers follow the same conventions, so the same Interfaces.C might work for all C compilers -- if that's true, then the Ada compiler will only need one Interfaces.C. The above scenario is for cases where the other language has different and incompatible compilers. So you might see Interfaces.This_Lisp and Interfaces.That_Lisp. -- Bob Duff bobduff@inmet.com Oak Tree Software, Inc. Ada 9X Mapping/Revision Team (Intermetrics, Inc.)