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 2002:a05:620a:1249:: with SMTP id a9mr652867qkl.147.1575316287918; Mon, 02 Dec 2019 11:51:27 -0800 (PST) X-Received: by 2002:a05:6830:1e37:: with SMTP id t23mr615504otr.16.1575316287618; Mon, 02 Dec 2019 11:51:27 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!news.gegeweb.eu!gegeweb.org!usenet-fr.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!g89no10734179qtd.0!news-out.google.com!o19ni923qtr.1!nntp.google.com!g89no10734170qtd.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Mon, 2 Dec 2019 11:51:26 -0800 (PST) In-Reply-To: <1f64ab89-81b4-4f26-a414-f3e1f53507ca@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=85.168.13.206; posting-account=iV1hDQoAAADj-LMkLVCARAp8f-n9fYeB NNTP-Posting-Host: 85.168.13.206 References: <9bee64ac-42c4-495e-9ce6-69c306b8e3a5@googlegroups.com> <1f64ab89-81b4-4f26-a414-f3e1f53507ca@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: yes another gnat bug (inherited tagged type as record field is too much for gnat??) From: George Shapovalov Injection-Date: Mon, 02 Dec 2019 19:51:27 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader01.eternal-september.org comp.lang.ada:57623 Date: 2019-12-02T11:51:26-08:00 List-Id: On Monday, December 2, 2019 at 6:12:04 PM UTC+1, Optikos wrote: > We should use this as an example to see how timely this gets fixed in=20 > FSF GNAT, to see whether it is measured in hours, days, weeks, months, et= c.=20 > over in FSF GNAT. That wouldn't be a fair comparison, nor a useful one. Please note, as I sai= d, the fix is in their *development* tree. Meaning that its not yet availab= le to the vast majority of users. maybe some -pro users with a special subs= cription have access to the "nightly builds" or something like that (I don;= t know how that works with AdaCore), but I would guess that even most -pro = users would get it only with the next release, after proper integration and= testing. Likely at a similar time it would become available to the community builder= s and testers - including FSF people. As far as I understand the arrangemen= t, AdaCore would be essentially an "upstream" for the FSF people, who would= then integrate Ada-specific features into public gcc backend that they mai= ntain [1]. And only then, with the next release of FSF/gpl version would it= fall into the hands of the "final" distro-level package maintainers and wo= uld normally get pushed out to the public with the next release or update o= f a correspondiong distro (some immediately, some with a new distro version= only - depending on package update policy of that distro). The whole process is sequential, with an established workflow, even schedul= es.. So, the "who gets it done faster" comparison is rather pointless here. [1]. No inside knowledge to the specifics here, only general experience how= it all works on a more public level, as a former (original, many years ago= ) maintainer of Ada in Gentoo Linux). But I am pretty sure they are not rei= mplementing the fixes and features in the Ada-specific code, when it is reg= ularly released y a reliable upstream. That would be contrary to "the spiri= t" and outright impractical and prone to introducing unnecessary problems..