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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,c406e0c4a6eb74ed
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: g2news1.google.com!postnews2.google.com!not-for-mail
From: kevin.cline@gmail.com (Kevin Cline)
Newsgroups: comp.lang.ada
Subject: Re: ADA Popularity Discussion Request
Date: 5 Sep 2004 15:49:44 -0700
Organization: http://groups.google.com
Message-ID: <e749549b.0409051449.574ec9ce@posting.google.com>
References: <49dc98cf.0408110556.18ae7df@posting.google.com>
 <cgpma7$pet$1@a1-hrz.uni-duisburg.de>
 <slrncj0nmf.hl6.adi@ppc201.mipool.uni-jena.de>
 <cgppvn$t4m$1@a1-hrz.uni-duisburg.de>
 <6F2Yc.848$8d1.621@newsread2.news.pas.earthlink.net>
 <m3isb2ey3w.fsf@rigel.goldenthreadtech.com>
 <hMnYc.1759$w%6.1486@newsread1.news.pas.earthlink.net>
 <m3656vfgmf.fsf@rigel.goldenthreadtech.com>
 <e749549b.0409042036.5d4822a2@posting.googlOrganization: LJK Software
 <vpblkhspuA9F@eisner.encompasserve.org>
NNTP-Posting-Host: 170.215.188.80
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1094424584 12107 127.0.0.1 (5 Sep 2004 22:49:44
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Sun, 5 Sep 2004 22:49:44 +0000 (UTC)
Xref: g2news1.google.com comp.lang.ada:3347
Date: 2004-09-05T15:49:44-07:00
List-Id: <comp.lang.ada>

Kilgallen@SpamCop.net (Larry Kilgallen) wrote in message news:<vpblkhspuA9F@eisner.encompasserve.org>...
> In article <iWG_c.8033$w%6.3982@newsread1.news.pas.earthlink.net>, "Richard  Riehle" <adaworks@earthlink.net> writes:
> 
> > No one argues that testing is unimportant.
>  
> > No language can protect us, at compile time, from every possible
> > error.
> 
> But assuming perfect testing, finding the errors during compilation
> rather than in testing saves me time, and time is money.

I thought so too, until I tried incremental test-first development. 
Retesting a unit after adding a few lines of code means that type
mismatches are caught immediately with or without strong typing.  But
it goes faster if you don't have to compile and link every iteration.