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,7332b19c66a79eea X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news3.google.com!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Thu, 18 Nov 2010 16:51:04 +0100 From: Georg Bauhaus User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Quantified Expressions: "some" References: <4ce31bb6$0$7670$9b4e6d93@newsspool1.arcor-online.net> <2d44ff4d-b3ad-4593-8492-4d16fb6b6a2e@j2g2000yqf.googlegroups.com> <1t7pvrh3i022d.8t9yqjonagar$.dlg@40tude.net> <4ce3e3c3$0$6987$9b4e6d93@newsspool4.arcor-online.net> <13vas9njbsmps.1npsunlgz5n4z$.dlg@40tude.net> <949be87b-78a2-4e7b-8b38-40f57a69eb55@d20g2000yqg.googlegroups.com> <8kknp7FkqpU1@mid.individual.net> In-Reply-To: <8kknp7FkqpU1@mid.individual.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-ID: <4ce54b69$0$7656$9b4e6d93@newsspool1.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 18 Nov 2010 16:51:05 CET NNTP-Posting-Host: 35ddbb8d.newsspool1.arcor-online.net X-Trace: DXC=c@VbY0nh0oBFJ3]dH>I?oEic==]BZ:afN4Fo<]lROoRA<`=YMgDjhgB`^X5QCGVNoCnc\616M64>JLh>_cHTX3jM0IkAjn9I_nM X-Complaints-To: usenet-abuse@arcor.de Xref: g2news2.google.com comp.lang.ada:16557 Date: 2010-11-18T16:51:05+01:00 List-Id: On 18.11.10 14:24, Niklas Holsti wrote: >> Use a colon or double colon: >> >> ( for all X in 1 | 3..5 | F'Range :: P(X) ) > > I like that. The double-colon is visually more apparent than '|' and there is > no risk of confusion with the earlier and other meanings of "=>". A single > colon could also work, if we don't want to add new lexemes. > Ad double colon, ::, adds to confusion if you work cross-language.