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, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,b78c363353551702 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.68.223.40 with SMTP id qr8mr10499021pbc.0.1340553990825; Sun, 24 Jun 2012 09:06:30 -0700 (PDT) Path: l9ni14963pbj.0!nntp.google.com!news2.google.com!goblin1!goblin2!goblin.stu.neva.ru!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: about the new Ada 2012 pre/post conditions Date: Sun, 24 Jun 2012 18:06:28 +0200 Organization: cbb software GmbH Message-ID: <1bbvp3ghpjb5s.1go1s1qvcmagh$.dlg@40tude.net> References: <1hgo6aks03zy.by4pq4xbjsgf$.dlg@40tude.net> <1jvy3elqtnd1j.1sjbk32evhp1f$.dlg@40tude.net> <1oih2rok18dmt.avbwrres5k12.dlg@40tude.net> <4fe59ea0$0$9502$9b4e6d93@newsspool1.arcor-online.net> <1mkp7fzlk1b0y.1ueinfjn48fcy$.dlg@40tude.net> <4fe72b6b$0$9504$9b4e6d93@newsspool1.arcor-online.net> Reply-To: mailbox@dmitry-kazakov.de NNTP-Posting-Host: q1gJPV1SC/KP9ydRbYoWiw.user.speranza.aioe.org Mime-Version: 1.0 X-Complaints-To: abuse@aioe.org User-Agent: 40tude_Dialog/2.0.15.1 X-Notice: Filtered by postfilter v. 0.8.2 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Date: 2012-06-24T18:06:28+02:00 List-Id: On Sun, 24 Jun 2012 16:59:55 +0200, Georg Bauhaus wrote: > On 23.06.12 13:01, Dmitry A. Kazakov wrote: >> Compare: a contract violation is an *unbounded ERROR*. > > Do you mean, I should imagine a contract violation that, > when checks are turned off, result in erroneous execution? The effect of contract violation is unbounded because not contracted. When you say that something behaves in a certain way under specified conditions, e.g. raises exception when out of range, that is the contract. 1. violation => nothing guaranteed 2. effect is bounded => these bounds are in the contract 1+2 = contract violation is necessarily *equivalent* to undefined behavior. What is so difficult about this? -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de