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 10.31.124.8 with SMTP id x8mr6754484vkc.10.1487679320722; Tue, 21 Feb 2017 04:15:20 -0800 (PST) X-Received: by 10.157.17.114 with SMTP id p47mr1636511otp.6.1487679320566; Tue, 21 Feb 2017 04:15:20 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!2.eu.feeder.erje.net!feeder.erje.net!2.us.feeder.erje.net!newspeer1.nac.net!border2.nntp.dca1.giganews.com!nntp.giganews.com!h53no593422qth.0!news-out.google.com!78ni88itm.0!nntp.google.com!e137no2037170itc.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 21 Feb 2017 04:15:19 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=76.218.37.33; posting-account=W2gdXQoAAADxIuhBWhPFjUps3wUp4RhQ NNTP-Posting-Host: 76.218.37.33 References: <864b4b14-5c42-4ddc-92ee-ad76ce2be159@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <55282a80-cc54-4901-9cfd-1a9ee273be1b@googlegroups.com> Subject: Re: relax double parens in expression_function_declaration? From: Stephen Leake Injection-Date: Tue, 21 Feb 2017 12:15:20 +0000 Content-Type: text/plain; charset=UTF-8 Xref: news.eternal-september.org comp.lang.ada:33373 Date: 2017-02-21T04:15:19-08:00 List-Id: On Monday, February 20, 2017 at 4:03:24 PM UTC-6, Randy Brukardt wrote: > "Stephen Leake" wrote: > > Recent GNAT allows this: > > > > type Result is record > > A : Integer; > > B : Integer; > > end record; > > > > function Key return Result is > > (A => 1, > > B => 2); > > > > However, I can't find a rule in the ARM that allows it. > > You're looking at the wrong version of the RM, then: that was fixed in the > Corrigendum. Ah. I was looking at the info version; I guess it's time to update that to include the Corrigendum.