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-Thread: 103376,c406e0c4a6eb74ed
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news1.google.com!news.glorb.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!feed2.news.rcn.net!rcn!feed3.news.rcn.net!not-for-mail
Sender: jsa@rigel.goldenthreadtech.com
Newsgroups: comp.lang.ada
Subject: Re: ADA Popularity Discussion Request
References: <49dc98cf.0408110556.18ae7df@posting.google.com>
 <cgn7bm$snk$3@a1-hrz.uni-duisburg.de>
 <e749549b.0408271348.74f5a957@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.google.com>
 <87eklg62x8.fsf@news.bourguet.org>
From: jayessay <nospam@foo.com>
Organization: Tangible
Date: 06 Sep 2004 12:45:28 -0400
Message-ID: <m3sm9ve47r.fsf@rigel.goldenthreadtech.com>
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: 
 DXC=HeaLm4HH^^]BSY?2J=<a4]0R]m=BkYWIW:6bU3OT9S9ZoBImG[Uf_IXLjhDjIjS^>Q[g\aJk;3HK^
X-Complaints-To: abuse@rcn.com
Xref: g2news1.google.com comp.lang.ada:3389
Date: 2004-09-06T12:45:28-04:00
List-Id: <comp.lang.ada>

Jean-Marc Bourguet <jm@bourguet.org> writes:

> kevin.cline@gmail.com (Kevin Cline) writes:
> 
> > Once you decide to test code before you write it, strong
> > typing loses most of it's value.
> 
> Well, I've been told that the earlier you detect an error,
> the easier and the cheaper it was to fix it.

Absolutely.


>  Errors detected by strong type checking are found earlier than
> those detected by testing.

Not if the testing is the sort used in bottom-up dynamic incremental
development.  There you are often testing both the "type constraints"
_and_ logic at the subexpression level up through clause and finally
to function!  This is way earlier and faster than any static type
checking.  It is also more robust as it is checking a lot more over a
far greater set of code paths.


/Jon

-- 
'j' - a n t h o n y at romeo/charley/november com