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=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,9da298537a16487e X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1995-01-26 09:16:48 PST Path: pad-thai.cam.ov.com!bloom-beacon.mit.edu!spool.mu.edu!olivea!nntp-sc.barrnet.net!barrnet.net!rational.com!kdm From: kdm@puppy.rational.com (Kent Mitchell) Newsgroups: comp.lang.ada Subject: Re: Run-time checking and speed Date: 26 Jan 1995 16:14:39 GMT Organization: Rational Software Corporation Message-ID: <3g8hpf$pn@rational.rational.com> References: <3ev16u$ojc@pong.lasc.lockheed.com> <3f3deb$4us@gnat.cs.nyu.edu> <3fa2pk$kbi@felix.seas.gwu.edu> <3fu902$6al@felix.seas.gwu.edu> <3g1eku$lmd@gnat.cs.nyu.edu> NNTP-Posting-Host: puppy.rational.com X-Newsreader: TIN [version 1.2 PL2] Date: 1995-01-26T16:14:39+00:00 List-Id: Robert Dewar (dewar@cs.nyu.edu) wrote: : Mike, you miss the point that in some environments it is REQUIRED to turn : off runtime checking. : Why, because runtime checking can create code that cannot be executed, and : in some verification environments coverage testing is required, so you cannot : have code and logic paths that cannot be executed. Can you explain how runtime checking can create code that cannot be executed. It would seem that if the checking code is in there is *is* going to do the check. I've worked on a lot of "safety critical" software projects and I've never seen the checks turned off because of the reason you state (though I've seen a lot of other reasons). -- Kent Mitchell | One possible reason that things aren't Technical Consultant | going according to plan is ..... Rational Software Corporation | that there never *was* a plan!