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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fac41,2c6139ce13be9980 X-Google-Attributes: gidfac41,public X-Google-Thread: f43e6,2c6139ce13be9980 X-Google-Attributes: gidf43e6,public X-Google-Thread: 103376,3d3f20d31be1c33a X-Google-Attributes: gid103376,public X-Google-Thread: 1108a1,2c6139ce13be9980 X-Google-Attributes: gid1108a1,public From: Ted Velkoff Subject: Re: Safety-critical development in Ada and Eiffel Date: 1997/08/18 Message-ID: <33F7D014.70B5@erols.com>#1/1 X-Deja-AN: 264932319 References: <33E9ADE9.4709@flash.net> <33F133D7.71AC@erols.com> <33F25933.7F83@flash.net> <33F27B5C.6A3C@erols.com> <33F44261.7BD3@flash.net> <33F527C8.32B3@erols.com> <33F5D274.30C4@flash.net> Organization: Erol's Internet Services X-Received-On: 18 Aug 1997 04:28:06 GMT Newsgroups: comp.object,comp.software-eng,comp.lang.ada,comp.lang.eiffel Date: 1997-08-18T00:00:00+00:00 List-Id: Ken Garlington wrote: > > Ted Velkoff wrote: > > To begin with, by "_always_ turned off", I assume what is meant is > > "turned off during execution of a delivered system", not "turned off > > during execution of a delivered system and during its entire development > > phase".[...] > > Not how the original argument was phrased. However if you want to argue > the merits of turning them on during development and then off for > released > code, see section 3.2.2 of > > http://www.flash.net/~kennieg/ariane.html > > for my rebuttal. > All the points made in section 3.2.2 are valid (meeting deadlines, issues in regression testing, limits to development resources). But is it really never appropriate to monitor assertions at any time in the development life-cycle? Forget about Eiffel for a moment, and consider Ada. I'm starting to think that the approach being advocated would suggest using "pragma Supress" throughout the entire development cycle, starting with unit test. Without ever having tried to do things that way, it seems on the surface that it would be harder to detect and correct bugs in the early going. Isn't there some amount of run-time checking that is appropriate during development even if it is turned off later? -- Ted Velkoff