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 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!v102.xanadu-bbs.net!xanadu-bbs.net!nntp.club.cc.cmu.edu!micro-heart-of-gold.mit.edu!newsswitch.lcs.mit.edu!nntp.TheWorld.com!.POSTED!not-for-mail From: Robert A Duff Newsgroups: comp.lang.ada Subject: Re: Studying and Maintaining GNAT, Is There Any Interest in a New Group? Date: Fri, 31 Aug 2018 17:23:27 -0400 Organization: The World Public Access UNIX, Brookline, MA Message-ID: References: <309225242.556906218.575482.laguest-archeia.com@nntp.aioe.org> <2145221813.556924687.162377.laguest-archeia.com@nntp.aioe.org> <0001HW.213464550E84375C70000C7DB2CF@news.individual.net> NNTP-Posting-Host: shell02.theworld.com Mime-Version: 1.0 Content-Type: text/plain X-Trace: pcls7.std.com 1535750607 24010 192.74.137.72 (31 Aug 2018 21:23:27 GMT) X-Complaints-To: abuse@TheWorld.com NNTP-Posting-Date: Fri, 31 Aug 2018 21:23:27 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:ZE0i3GnrqYjP0AV2rX2+Hd+0tqs= Xref: reader02.eternal-september.org comp.lang.ada:54303 Date: 2018-08-31T17:23:27-04:00 List-Id: Shark8 writes: > On Monday, August 27, 2018 at 10:54:48 AM UTC-6, Bill Findlay wrote: >> On 27 Aug 2018, Simon Wright wrote: >> > And there are bugs in the backend; e.g. currently some problems with >> > LTO/Darwin. >> >> Could you say more about that, Simon? >> It might explain some difficulties I have been experiencing. > Well, one bug that seems to recur frequently is mishandling of RENAMES, and not obscure renamings either, things like attribute renaming: > Length : Natural renames Some_Array'Length; That's illegal, because Some_Array'Length denotes a value, not an object, so you can't use it like that in an object_renaming_declaration. GNAT correctly detects this error. I don't see any mishandling here. Am I missing something? I would prefer to allow the above, but that's a language issue, not a compiler issue. And it's certainly not an issue specific to the back end. > (Though they might have special-cased this particular one.) Not sure what you mean by that. - Bob