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=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a37:a947:: with SMTP id s68mr1123064qke.168.1575320571103; Mon, 02 Dec 2019 13:02:51 -0800 (PST) X-Received: by 2002:a9d:66a:: with SMTP id 97mr823478otn.114.1575320570636; Mon, 02 Dec 2019 13:02:50 -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!g89no10902729qtd.0!news-out.google.com!o19ni930qtr.1!nntp.google.com!g89no10902721qtd.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Mon, 2 Dec 2019 13:02:50 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=47.185.234.173; posting-account=zwxLlwoAAAChLBU7oraRzNDnqQYkYbpo NNTP-Posting-Host: 47.185.234.173 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: <0f310d51-978b-463a-941e-a8d60b798fcc@googlegroups.com> Subject: Re: yes another gnat bug (inherited tagged type as record field is too much for gnat??) From: Optikos Injection-Date: Mon, 02 Dec 2019 21:02:51 +0000 Content-Type: text/plain; charset="UTF-8" Xref: reader01.eternal-september.org comp.lang.ada:57625 Date: 2019-12-02T13:02:50-08:00 List-Id: On Monday, December 2, 2019 at 1:51:29 PM UTC-6, George Shapovalov wrote: > 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 > > FSF GNAT, to see whether it is measured in hours, days, weeks, months, etc. > > over in FSF GNAT. > > That wouldn't be a fair comparison, nor a useful one. Quit putting words in my mouth. I never said that all AdaCore customers have this fix delivered to them today. I effectively said that 1) we know for a (purported reported) fact that the fix hit AdaCore's internal codebase today; 2) we can eventually observe the date at which this defect's fix hits FSF GNAT to see when OP's original symptoms are no longer exhibited by FSF GNAT. 3) we can then accurately calculate the time that it empirically can take for a fix to defect to actually get released to the wild in FSF GNAT. I did not say directly or by implication that FSF GNAT's lag is different than typical AdaCore paying customer's lag in receiving this fix. Although now that you bring it up, that would be a fascinating side topic. > Please note, as I said, the fix is in their *development* > tree. Meaning that its not yet available to the vast majority of users. maybe some -pro users with a special > subscription 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.