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.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.194.216.10 with SMTP id om10mr771588wjc.3.1466274279437; Sat, 18 Jun 2016 11:24:39 -0700 (PDT) X-Received: by 10.157.37.168 with SMTP id q37mr267827ota.13.1466274279324; Sat, 18 Jun 2016 11:24:39 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!goblin1!goblin.stu.neva.ru!w10no2456284lbo.0!news-out.google.com!di11ni25844lbb.1!nntp.google.com!w10no2456269lbo.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sat, 18 Jun 2016 11:24:39 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=67.0.53.185; posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC NNTP-Posting-Host: 67.0.53.185 References: <623218455.487799273.877639.laguest-archeia.com@nntp.aioe.org> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <7cc0e66f-2a45-4cca-b670-0c3859f4b004@googlegroups.com> Subject: Re: Ada and C++ in the same binary, was: Re: Current status of Ada development for an Android target ? From: Shark8 Injection-Date: Sat, 18 Jun 2016 18:24:39 +0000 Content-Type: text/plain; charset=UTF-8 Xref: news.eternal-september.org comp.lang.ada:30794 Date: 2016-06-18T11:24:39-07:00 List-Id: On Saturday, June 18, 2016 at 9:44:37 AM UTC-6, Simon Clubley wrote: > On 2016-06-16, Luke A Guest wrote: > > Simon Clubley wrote: > >> On 2016-06-16, Lucretia wrote: > >>> Just to update, the FSF GCC 4.9.2, 5.4.0 and 6.1.0 do not compile any of > >>> the 64 bit targets, they all fail. They are missing patches from Google > >>> and I don't think they will ever get passed upstream. > >> > >> Thanks for the update Luke. > >> > >> Simon. > >> > >> PS: And thanks for looking. > >> > > > > A quick way around this is I could build it based on the Google source > > for4.9 and leave extracting the patches to spot to FSF for later. That > > would work. > > > > Thanks Luke, but please don't go to any special effort on my behalf. > > Having thought about the situation, I'm getting nervous once again about > the "special" :-( situation around Ada compilers given that I'm not > sure where some of this code might be used in the future. Well, hopefully Byron will help push the available options up a bit. > My current thinking (as of this morning :-)) is to maybe write the low > level stuff in C++ (which is the code more likely to be used elsewhere) > and to do the high level stuff in Ada. I think I understand what you're saying... but wouldn't that invite errors in the lower levels? I rather like the focus that Ada puts on correctness. (And SPARK is pretty nifty, too.) > The problem is that I don't have any experience combining C++ and Ada > code in the same binary; in the past, I've only ever called plain C code > from Ada. What about writing it all in Ada and providing an export interface to C++?