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,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,75ce2ead897158b2 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit X-Received: by 10.224.219.146 with SMTP id hu18mr9611166qab.3.1364867536062; Mon, 01 Apr 2013 18:52:16 -0700 (PDT) X-Received: by 10.49.127.200 with SMTP id ni8mr1086686qeb.42.1364867536040; Mon, 01 Apr 2013 18:52:16 -0700 (PDT) Path: v17ni6816qad.0!nntp.google.com!ca1no20287987qab.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Mon, 1 Apr 2013 18:52:16 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=149.32.224.34; posting-account=Qh2kiQoAAADpCLlhT_KTYoGO8dU3n4I6 NNTP-Posting-Host: 149.32.224.34 References: <0c77e832-e12b-446d-af24-78d77c358f1e@googlegroups.com> <25ee066d-3270-4efd-829f-ed40b04c0655@googlegroups.com> <89292c53-1d4e-48a7-b2ae-a10983ef4168@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: My bug or else regarding Visibility Rules From: Anh Vo Injection-Date: Tue, 02 Apr 2013 01:52:16 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Date: 2013-04-01T18:52:16-07:00 List-Id: On Monday, April 1, 2013 5:56:19 PM UTC-7, Randy Brukardt wrote: > "Anh Vo" wrote in message news:89292c53-1d4e-48a7= -b2ae-a10983ef4168@googlegroups.com... > On Thursday, March 28, 2013 3:03:1= 3 PM UTC-7, Randy Brukardt wrote: >> "Adam Beneschan" wro= te in >>> the >> > keyword PRIVATE >> > when that keyword is present; but i= f you take it out, the declaration >> > list >> > ends at "end Circular_Que= ue;". >>=20 >>> Which is the long way to say that the expression of a public aspect has >>> be made up only of public functions and objects. Otherwise, how would a= =20 >>> caller be able to figure out the meaning of a precondition that they ar= e=20 >>> required to meet? Clients can never be required to look in a private=20 >>> part.=20 >> Actually, this part only involves post-conditions (implementer), not=20 >> preconditions (clients).=20 >Clients need to know about postconditions as well, so that they know what = >properties are guaranteed after a call. Typically, that will show that=20 >some or all of a following precondition is going to be satisfied. Remember= , >both of these matter to both sides of a call: A precondition is a requir= ement >on a caller and a promise to an implementation; a postcondition is a= promise >to a caller and a requirement on an implementation. Randy. I try to put as much as post-conditions that the language allows. On the ot= her hand, I do not want to expose any thing that the clients can modify. In= addition, taking away post-conditions involving Buffer, In_Index, and Out_= Index objects by moving them into the body does degrade much implementation= promise in this case. A. Vo =20