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.58.77 with SMTP id f13mr1312172qah.7.1364926643694;
        Tue, 02 Apr 2013 11:17:23 -0700 (PDT)
X-Received: by 10.49.104.144 with SMTP id ge16mr1443272qeb.19.1364926643653;
 Tue, 02 Apr 2013 11:17:23 -0700 (PDT)
Path: 
 v17ni6816qad.0!nntp.google.com!ca1no21100101qab.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Tue, 2 Apr 2013 11:17:23 -0700 (PDT)
In-Reply-To: <lywqslgwyj.fsf@pushface.org>
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>
 <kj2en4$9q1$1@munin.nbi.dk>
 <89292c53-1d4e-48a7-b2ae-a10983ef4168@googlegroups.com>
 <kjdabm$dck$1@munin.nbi.dk>
 <d09afc35-2ca5-4b45-9734-7263e6d353c4@googlegroups.com>
 <lywqslgwyj.fsf@pushface.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <e703d782-2e4c-4fe9-bcae-218abcc170f1@googlegroups.com>
Subject: Re: My bug or else regarding Visibility Rules
From: Anh Vo <anhvofrcaus@gmail.com>
Injection-Date: Tue, 02 Apr 2013 18:17:23 +0000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Date: 2013-04-02T11:17:23-07:00
List-Id: <comp.lang.ada>

On Tuesday, April 2, 2013 1:26:12 AM UTC-7, Simon Wright wrote:
Other recipients:=20
Anh Vo <anhvo...@gmail.com> writes:=20
> This is (partly) why we now have expression functions; specify the=20
> function in the public part, use it in a pre/postcondition, complete it=
=20
> with an expression function in the private part when Buffer etc. are=20
> visible.=20

It is dangerous make internal data visible in this case. after careful cons=
ideration, I decided to take away part of the post-conditions rather than e=
xposing them. Following the philosophy of Ada, I would not leave any possib=
ilities for the clients to accidently mess it up (not allowing clients to s=
hoot themselve in the foot)