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 X-Google-Thread: 103376,31c633ee5da73ed9 X-Google-Attributes: gid103376,public From: gisle@apal.ii.uib.no (Gisle S�lensminde) Subject: Re: Ada and C++; Any Gurus Out There? Date: 1999/06/03 Message-ID: #1/1 X-Deja-AN: 485322427 Content-Transfer-Encoding: 8bit References: <7j4lua$2rs$1@nnrp1.deja.com> Organization: University of Bergen, Norway Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 1999-06-03T00:00:00+00:00 List-Id: In article <7j4lua$2rs$1@nnrp1.deja.com>, Robert Dewar wrote: >In article , > gisle@apal.ii.uib.no (Gisle S�lensminde) wrote: >> Using 'extern C' is not a workaround, but the intended >> solution. > >No, that's not quite right, there *was* no "intended solution". >Why not? Because at the time Ada 95 designed there was not >officially standardized C++ language, so the Ada 95 standard >could not address this particular issue. I did not think about the Ada95 design, but that of C++. It is specified in the C++ standard that there is a C++ linkage convention, which differs from the C convention, so 'extern C' is neccesary to make C linkage, and not a workaround. -- Gisle S�lensminde ( gisle@ii.uib.no )