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.4 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,4cb1f8d1c17d39a8 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.68.16.35 with SMTP id c3mr6814995pbd.6.1319921557996; Sat, 29 Oct 2011 13:52:37 -0700 (PDT) Path: p6ni27003pbn.0!nntp.google.com!news1.google.com!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post01.iad.highwinds-media.com!newsfe17.iad.POSTED!00000000!not-for-mail From: Brad Moore User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Ada 'hello world' for Android; success! References: <8239efcjuw.fsf@stephe-leake.org> <98ca5430-aa52-4e39-b789-70d0dd6adb46@d33g2000prb.googlegroups.com> <824nyrq5p6.fsf@stephe-leake.org> <4eac1ca1$0$7625$9b4e6d93@newsspool1.arcor-online.net> In-Reply-To: Message-ID: NNTP-Posting-Host: 184.64.75.84 X-Complaints-To: internet.abuse@sjrb.ca X-Trace: newsfe17.iad 1319921478 184.64.75.84 (Sat, 29 Oct 2011 20:51:18 UTC) NNTP-Posting-Date: Sat, 29 Oct 2011 20:51:18 UTC Date: Sat, 29 Oct 2011 14:51:16 -0600 Xref: news1.google.com comp.lang.ada:18755 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Date: 2011-10-29T14:51:16-06:00 List-Id: On 29/10/2011 10:09 AM, Simon Wright wrote: > Georg Bauhaus writes: > >> Is the traditional O-O model of Ada impossible to support >> in a compiler for Android devices or is it just that no one >> is paying for such a compiler? So that the best we can do is >> juggle the pointers that the other languages can hide? > > I'd have thought it was more a problem of the bindings being > thin? Making thick bindings to a moving target is quite a challenge, of > course. That can be one of the advantages of a thick binding though. It can insulate client code from changes to the lower level API, (as long as the low level changes aren't too drastic) It just takes someone to maintain the bindings.