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,624801e212a1e237 X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: Ada bindings to C++ Date: 1996/12/06 Message-ID: #1/1 X-Deja-AN: 202817799 references: <32A606B9.5A66@llnl.gov> <32A84CF4.794B@cpmx.saic.com> organization: New York University newsgroups: comp.lang.ada Date: 1996-12-06T00:00:00+00:00 List-Id: John Cosby said "It's not that simple. The representation of C++ objects is entirely compiler- dependent, as is the representation of Ada95 tagged types. You cannot imply a mapping between different compilers (GNAT and g++ form an exception; since both use the same compiler engine, they use the same representation, and can swap objects to some degree). In many programming environments, there is no way to (for example) make Ada95 invoke C++ object methods, or have C++ call Ada95 dispatching functions." Please note that GNAT has an entirely procedural interface for defining the format of dispatching tables, so by modifying the appropriate runtime routine, it is possible to "make Ada 95 invoke C++ object methods", for virtually any C++ compiler, not just g++ (interfacing to g++ is neither harder or easier than interfacing to any other C++ compiler from GNAT).