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=-0.3 required=5.0 tests=BAYES_00,FREEMAIL_FROM, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,103b407e8b68350b X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-01-07 05:36:39 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!canoe.uoregon.edu!arclight.uoregon.edu!news.infoave.net!newsfeed1.easynews.com!easynews.com!easynews!cyclone.swbell.net!bos-service1.ext.raytheon.com!bos-service2.ext.raytheon.com.POSTED!not-for-mail From: Wes Groleau Reply-To: wesgroleau@despammed.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en,es-MX,es,pt,fr-CA,fr MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Anybody in US using ADA ? One silly idea.. References: <3E147D79.2070703@cogeco.ca> <4519e058.0301031434.51a0c880@posting.google.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Message-ID: Date: Tue, 07 Jan 2003 08:36:27 -0500 NNTP-Posting-Host: 151.168.133.155 X-Complaints-To: news@ext.ray.com X-Trace: bos-service2.ext.raytheon.com 1041946598 151.168.133.155 (Tue, 07 Jan 2003 08:36:38 EST) NNTP-Posting-Date: Tue, 07 Jan 2003 08:36:38 EST Organization: Raytheon Company Xref: archiver1.google.com comp.lang.ada:32675 Date: 2003-01-07T08:36:27-05:00 List-Id: > Of course, 'First and 'Last imply a range. Ranges imply > discrete values. How would you describe the range for > a type that is not discrete? This would imply the ability to > define discontinuous ranges. Although that ability seems > convenient for the programmer, I have no idea how it could > be implemented by the compiler writer in an efficient and > general manner. The compiler writer would not need to implement it. Just the ability for the USER to define it. The application is a type that conceptually has a range, but is for some reason private. >>It would also be nice to be able to redefine 'Size >>for an access type or record containing an access type. > > Defining 'Size for an access type would require a consistent > implementation of access types across all compilers. Remember No, the USER wants to redefine it so that it is somehow related to the value pointed to. The implementation is irrelevant. It's to would support the abstraction, not the implementation. But, I repeat, these are _minor_ issues.