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!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: Ada.Real_Time.Time_Last Date: Sat, 18 Nov 2017 17:01:09 +0100 Organization: Aioe.org NNTP Server Message-ID: References: <591a9389-a4b8-43fa-b963-0ebb9e488be1@googlegroups.com> NNTP-Posting-Host: MajGvm9MbNtGBKE7r8NgYA.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 Content-Language: en-US X-Notice: Filtered by postfilter v. 0.8.2 Xref: feeder.eternal-september.org comp.lang.ada:48991 Date: 2017-11-18T17:01:09+01:00 List-Id: On 2017-11-18 16:24, Niklas Holsti wrote: > Making Count'First and Count'Last available is part of the goal of the > extension, but the point is that the *expressions* that define their > values would still be *private*, which means that the user of the type > cannot (or is not meant to) depend on those expressions. The user can > access the end result ('First, 'Last) but is not meant to depend on any > other properties of those expressions. The proposal should also encompass other cases where information hiding principle gets violated, e.g.: procedure Foo (I : Integer := 20); If I don't want to expose the default or when the parameter is a private type, I should be able to provide a private value, just like in your case: type Count is range 0..; Same applies to the defaults of record type members, BTW. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de