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.8 required=5.0 tests=BAYES_00,PLING_QUERY autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,b6d862eabdeb1fc4 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news3.google.com!feeder2.cambriumusenet.nl!feed.tweaknews.nl!87.79.20.105.MISMATCH!news.netcologne.de!ramfeed1.netcologne.de!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Sun, 06 Jun 2010 23:22:15 +0200 From: Georg Bauhaus User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Ada noob here! Is Ada widely used? References: <0e88de66-128c-48fd-9b9f-fdb4357f318a@z17g2000vbd.googlegroups.com> <2o8vq76hpv1m.vs7m2beo23nz.dlg@40tude.net> <1q5k4indthpli.1dn17o4ue4a15$.dlg@40tude.net> In-Reply-To: <1q5k4indthpli.1dn17o4ue4a15$.dlg@40tude.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <4c0c1188$0$6887$9b4e6d93@newsspool2.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 06 Jun 2010 23:22:16 CEST NNTP-Posting-Host: 8c88bdba.newsspool2.arcor-online.net X-Trace: DXC=XcoOhL6VB[8U`5g[@c]@J1A9EHlD;3Yc24Fo<]lROoR18kF On 6/6/10 3:10 PM, Dmitry A. Kazakov wrote: >>> Some, but as I said Ada drifts towards less checks. >> Really ? I don't feel so much and don't believe most interested parties >> will allow it. >> The introduction of DbC in the Ada 2012 language itself, even goes the >> opposite way. Isn't it ? > > You forgot that run-time check is not a check to me. It is a language > design bug. I am afraid I will like Ada 2012 even less than Ada 2005. It seems worthwhile mentioning that DbC's primary purpose is not to augment programs with run-time checks; rather, DbC asks for programmers who write as if there was no assertion monitoring but who explain their code with pre/post/inv. The operator may turn on run-time monitoring so that he/she is notified if something goes wrong (disproving the programmers' assumptions; the monitor stops the program or runs the remains in a debugger).