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 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,34c5e4948f429691 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news3.google.com!news.germany.com!newsfeed2.scan-plus.net!newsfeed.ision.net!newsfeed2.easynews.net!ision!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail Newsgroups: comp.lang.ada Subject: Re: ANN: QtAda preview available From: Georg Bauhaus In-Reply-To: <46232421$1@news.post.ch> References: <1176378179.964724.176000@w1g2000hsg.googlegroups.com> <1201303.5dLqL8CvEh@linux1.krischik.com> <1176699587.727008.107400@q75g2000hsh.googlegroups.com> <46232421$1@news.post.ch> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1176738035.8013.15.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 Date: Mon, 16 Apr 2007 17:40:36 +0200 Organization: Arcor NNTP-Posting-Date: 16 Apr 2007 17:35:33 CEST NNTP-Posting-Host: b3a57957.newsspool4.arcor-online.net X-Trace: DXC=leMZYdDJ4OE78PK[oJ2ng@4IUK On Mon, 2007-04-16 at 09:22 +0200, Martin Krischik wrote: > vgodunko@rostel.ru schrieb: > > On Apr 15, 1:28 pm, Martin Krischik > > wrote: > >> Which compiler are you using? > >> > > GNAT Pro 6.1.0w (20070321-41) > > > > This is minimum GNAT version which able to compile QtAda :( > > A "wavefront" compiler. Now you are aware that wavefront are specialy > made for your project. We only can hope the patches make it into GPL > 2007 - which AdaCore currently prepares. Otherwise we need to wait for > GCC 4.3.0 and GPL 2008 for QtAda :-( . Some of the issues (the style checks can be disable by something like find . -name Makefile\* | \ xargs perl -pi'*_orig' -e 's/-gnatyaA/-gnatya/' prior to running configure) seem to be caused by heavy use of 2005 style access together with type conversions of .all objects. Is this by necessity, or is it more like a consequence of translating C++ style references into Ada access parameters? (Maybe then the binding can profit from cont T& correspond to just "in", not "access not null"?)