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,73cb216d191f0fef X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit X-Received: by 10.180.183.84 with SMTP id ek20mr428865wic.0.1363253233674; Thu, 14 Mar 2013 02:27:13 -0700 (PDT) Path: bp2ni91402wib.1!nntp.google.com!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Thu, 14 Mar 2013 10:27:12 +0100 From: Georg Bauhaus User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Is this expected behavior or not References: <8klywqh2pf$.1f949flc1xeia.dlg@40tude.net> <513f6e2f$0$6572$9b4e6d93@newsspool3.arcor-online.net> <513faaf7$0$6626$9b4e6d93@newsspool2.arcor-online.net> <51408e81$0$6577$9b4e6d93@newsspool3.arcor-online.net> <1xqmd3386hvns.1og1uql2cgnuf$.dlg@40tude.net> <5140b812$0$6575$9b4e6d93@newsspool3.arcor-online.net> In-Reply-To: Message-ID: <514197f0$0$6623$9b4e6d93@newsspool2.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 14 Mar 2013 10:27:13 CET NNTP-Posting-Host: 20d0ed6d.newsspool2.arcor-online.net X-Trace: DXC=[YTcaPkQ:IF78PK[oJ2ng@A9EHlD;3YcB4Fo<]lROoRA8kFJLh>_cHTX3jMo4`08^Z9ECA X-Complaints-To: usenet-abuse@arcor.de Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Date: 2013-03-14T10:27:13+01:00 List-Id: On 14.03.13 10:09, Dmitry A. Kazakov wrote: > And it must be said that > a declaration like > > type T is range A..B; > > is a shortcut for a more explicit declaration of T inheriting interfaces of > a scalar object, a comparable object, a numeric object, an ordered object, > a copyiable object etc. +1 With the proviso that the compatibility obstacle requires restraint, I'd suggest type R is abstract range 0 .. 1; type T is abstract new Float; as a starting point. Is "abstract ..." compatible with previous versions of the language?