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,e7ceb00d83425e3a
X-Google-Attributes: gid103376,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news2.google.com!news1.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!t-online.de!feeder.news-service.com!feeder1.cambrium.nl!feed.tweaknews.nl!not-for-mail
From: Ludovic Brenta <ludovic@ludovic-brenta.org>
Newsgroups: comp.lang.ada
Subject: Prototyping with Ada (was: Ada featured in Doctor Dobb's Journal)
References: 
 <31a97103-1cbb-47b5-a93c-2a29c206556f@e39g2000hsf.googlegroups.com>
	<0d254195-50cb-4bad-b776-8d5c2ab09b6c@m45g2000hsb.googlegroups.com>
	<ba91fec6-cfc1-4b48-ad96-fa2a233e66f4@u36g2000prf.googlegroups.com>
	<878wy9uyg9.fsf@ludovic-brenta.org>
	<d419cb3c-da09-42f8-98a6-75bba927167c@w4g2000prd.googlegroups.com>
	<87zlqptajv.fsf@ludovic-brenta.org>
	<7f3435c6-bacb-4e02-a1de-2e73a417ba6c@w4g2000prd.googlegroups.com>
	<87r6c0sei2.fsf@ludovic-brenta.org>
	<pan.2008.05.18.00.35.38.923802@linuxchip.demon.co.uk.uk.uk>
Date: Sun, 18 May 2008 10:04:17 +0200
Message-ID: <87k5hsrqbi.fsf_-_@ludovic-brenta.org>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
Cancel-Lock: sha1:OkoLFW5vhr7pBmxM0ADX1RmQz1U=
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Organization: Tele2
X-Trace: 
 DXC=fB;2[]]a0iI8KY=8ilHV4D6`Y6aWje^YJ3aQ=dR3h2`LCQ4^CaAC7>A`o1cc]__2cMigLd:l\]nHF
Xref: g2news1.google.com comp.lang.ada:192
Date: 2008-05-18T10:04:17+02:00
List-Id: <comp.lang.ada>

Dr. Adrian Wrigley writes
> I think Ada is great for prototyping too.
>
> Often, the code is in great flux when prototyping, and the Ada features
> really work in your favor by ensuring consistency and catching the
> mistakes early.
>
> For very prototyping simple projects, scripting languages are fast,
> but errors and inconsistencies creep in quickly.  The code tends not
> to last as long because of inflexibility (poor/missing structuring tools
> such as packages and generics in scripting).

I agree.  I would even go so far as to say there is no such thing as
software prototyping.  A prototype is something complex you make
before mass-producing some sort of physical good, because it is very
difficult to change the physical system after you've made it, should
you find any problems.  By definition, you know you're going to throw
the prototype away at some point.

The opposite is true for software.  If you build a prototype, you can
always fix problems in it.  And once there are no more problems, the
prototpye is the "real" software, and you don't throw anything away.
Which means the "prototype" you thought you made was not a prototype
after all; just an early and evolving version of the "real" software.

-- 
Ludovic Brenta.