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,de06245437f9462 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-06-19 09:15:07 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.mathworks.com!cyclone.swbell.net!bos-service1.ext.raytheon.com!dfw-service2.ext.raytheon.com.POSTED!not-for-mail Message-ID: <3D10AD0C.30017326@raytheon.com> From: Mark Johnson X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Linked List in ada References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 19 Jun 2002 11:10:52 -0500 NNTP-Posting-Host: 192.27.48.39 X-Complaints-To: news@ext.ray.com X-Trace: dfw-service2.ext.raytheon.com 1024503089 192.27.48.39 (Wed, 19 Jun 2002 11:11:29 CDT) NNTP-Posting-Date: Wed, 19 Jun 2002 11:11:29 CDT Organization: Raytheon Company Xref: archiver1.google.com comp.lang.ada:26392 Date: 2002-06-19T11:10:52-05:00 List-Id: tmoran@acm.org wrote: > > > Well, i haven't tried to compile it yet. I am anti error msgs :) > You need to get your mind turned around. An Ada compiler is not > just a necessary step to producing machine code, it's an assistant > helping you avoid error and get your program right. [snip...] Hmm. Let me provide a different opinion on that recommendation. If you use the compiler as a quality check on your code review, you can get a better quality product and better productivity. I might even recommend this strongly to the OP since it encourages good habits (stronger code review). Let me explain how that can work... If you have generated say 20 defects in a program and have two people do the compile and code review you might get the following results... #1 - compile flags 12 errors, code review removes 4 more (total 16), 4 left to find in unit test. #2 - compile flags 12 errors, code review removes 6 more (total 18), 2 left to find in unit test. Now do them in the other order... #1 - code review removes 10 errors, compiler flags 6 more (total 16), 4 left to find in unit test. #2 - code review removes 15 errors, compiler flags 3 more (total 18), 2 left to find in unit test. That the compiler found 6 instead of 3 errors for #1 is an indication that the code review was poor and should be repeated. The counter argument is usually that the compiler finds the errors faster than you do. I agree, but the cost of letting the two extra errors in unit test (say 1 hour to find and fix each) more than pays for the longer code review cycle. --Mark