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.1 required=5.0 tests=BAYES_40,INVALID_DATE,
	MSGID_SHORT autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!ssc-vax!shuksan!scott
From: scott@shuksan.UUCP (Scott Moody)
Newsgroups: comp.lang.ada
Subject: Re: Dynamic Typing in Ada
Summary: Prototype->Design->Recode
Message-ID: <1227@shuksan.UUCP>
Date: 24 Mar 89 18:42:43 GMT
References: <8903101703.AA04518@ti.com> <730@aoa.UUCP>
Distribution: usa
Organization: The Boeing Co., BAC MMST, Seattle, WA
List-Id: <comp.lang.ada>

I think the real issue is not to make Ada into something it
isn't. It isn't the greatest dynamic prototyping language,
but can still be used to prototype. 
Aside from the Ada Guru test of providing in Ada similar 
dynamic capabilities that other languages offer, I think we
are missing the real issue of "design" and "requirements". 

Once the prototyper has developed a nifty lisp/smalltalk/ai program, take the
"design/requirements" that the prototype generated 
and code it up in your favorite type safe language (Ada). 
A "design/requirements" shouldn't rely on dynamic typing 
(but an implementation may use these feature especially in a prototype).

-- Scott Moody