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,start X-Google-Attributes: gid103376,public From: "Brett M. Kettering" Subject: Ada bindings to C++ Date: 1996/12/04 Message-ID: <32A606B9.5A66@llnl.gov>#1/1 X-Deja-AN: 202392159 content-type: text/plain; charset=us-ascii organization: LLNL mime-version: 1.0 newsgroups: comp.lang.ada x-mailer: Mozilla 3.0 (X11; U; SunOS 5.5 sun4m) Date: 1996-12-04T00:00:00+00:00 List-Id: I have written Ada bindings to C in both Ada 83 and Ada 95. The Interfaces.C package and pragma Convention of Ada 95 really make this a lot easier. Lately I have been considering Ada 95 bindings to C++. Can I get some input from persons that have written Ada 95 bindings to C++? In my readings I have learned that the C++ class construct is analogous to the C struct. So, this would imply that a binding to a class becomes an Ada 95 record that contains pointers to functions, as well as the Ada 95 versions of C data, as its elements? What about class objects that are "thrown" as exceptions? How does one go about using pragmas Import and Convention to bring these functions into an Ada 95 program to be called? Does the "c2ada" translator convert C++ header files to Ada 95 bindings? Thanks for any leads. Brett -------------------------------------------------- Brett M. Kettering LLNL P.O. Box 808 L-493 Livermore, CA. 94550 E-mail: brettk@llnl.gov Voice : (510) 423-3467 FAX : (510) 422-1930 --------------------------------------------------