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: 103376,42427d0d1bf647b1 X-Google-Attributes: gid103376,public From: Ken Garlington Subject: Re: Ada Core Technologies and Ada95 Standards Date: 1996/04/15 Message-ID: <3172903D.1926@lfwc.lockheed.com>#1/1 X-Deja-AN: 147684681 references: <00001a73+00002c20@msn.com> <4kf739$f00@cliffy.lfwc.lockheed.com> content-type: text/plain; charset=us-ascii organization: Lockheed Martin Tactical Aircraft Systems mime-version: 1.0 newsgroups: comp.lang.ada x-mailer: Mozilla 2.01 (Macintosh; I; 68K) Date: 1996-04-15T00:00:00+00:00 List-Id: Robert Dewar wrote: > > In fact I think Ken *did* expect the ACVC to guarantee > compliance, and unfortunately this is not possible. Nope. _You_ keep claiming I said this, and I keep saying, "show me where I said this, and I will retract it." I asked two questions. Can you recall them? Probably not. > > >on the pathological cases and make a strong argument for doing nothing > >while we continue to develop safety critical code with *validated* > >compilers which generate bad code for some of the more simple Ada > >features. > > Unfortunately simple black box testing cannot even guarantee that 100% > of simple Ada features are completely accurately implemented. > > >Instead of flaming us for expecting to much, take our comments and > >feedback from your "larger" user community, and challenge yourself > >(i.e., the Ada compiler vendors) to provide a high quality > >product that meets all of our needs. > > Well of course, we certainly do aim at that. Aim at flaming users for expecting too much? Or aim at providing a high quality product? When you decide you can discuss the later issue without the bile rising, let me know. > The point is that the > black box testing of the ACVC suite can only be one part of that process. > At ACT for example, we have an extremely rigorous development process. > Among other steps we take, we run our complete regression suite.... Unfortunately, you don't have time to discuss steps 2-N. Let me know if you do. > As with most complex programming tasks, quality is achieved with a > multi-faceted approach. A regression test suite (which may or may not be a good one), and some other unspecified steps. Facets > 1? No way for me to tell! > The important thing is to realize that the ACVC can only ever be one > component of this multi-faceted approach... Unfortunately, real facets fit togethger. Does the ACVC fit with the other facets (e.g. at the vendor)? Should the ACVC grow (quantitatively or qualitatively)? Should it shrink? Who knows? Who will ever know, given the open hostility to discussing the subject?