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!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: Ada 2012 Constraints (WRT an Ada IR) Date: Wed, 14 Dec 2016 12:25:30 +0100 Organization: Aioe.org NNTP Server Message-ID: References: <999c67b0-4478-4d2b-8108-32ac48fe6316@googlegroups.com> NNTP-Posting-Host: vZYCW951TbFitc4GdEwQJg.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 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 X-Notice: Filtered by postfilter v. 0.8.2 Xref: news.eternal-september.org comp.lang.ada:32811 Date: 2016-12-14T12:25:30+01:00 List-Id: On 14/12/2016 12:04, G.B. wrote: > On 14/12/2016 09:42, Dmitry A. Kazakov wrote: >> >> The precondition here is *not* (Y in Positive), it is (Y in Integer). >> It is legal to call X on any Integer. Checking Y>=0 is semantically a >> part of the X's body, even if the compiler could inline this part at >> the caller's side or optimize it or the rest of the body away. > > And this is where Design by Contract, by intent, would differ > from current choice of Ada's defensive style: > > The programmer is NOT allowed to just call an operation > when there is a Pre aspect that says: Don't! So long the program remains legal that is not a contract from the language point of view. > So, by intent, if you declare > > procedure X (Y : Positive) > with > Pre => Y > 0; > > then a client programmer is required, by contract, to not > call X with a non-positive Integer. If he or she does, > then the programmer is violating the contract, and held > responsible for any damage caused by the body of X. It is about formal language-supported contracts and all sorts of other contracts. > This is what contract based programming is all about. That is the problem with implied contracts. Is this legal: begin loop X (Read (Stream)); end loop; exception when Constraint_Error => null; end; -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de