Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!edcastle!lfcs!nick
From: nick@lfcs.ed.ac.uk (Nick Rothwell)
Newsgroups: comp.object
Subject: Re: A Closer Look At the Recursive/Parallel (OO) Life-Cycle
Message-ID: <1487@castle.ed.ac.uk>
Date: 4 Jan 90 13:26:01 GMT
References: <16836@isvax.isl.melco.co.jp>
Reply-To: nick@lfcs.ed.ac.uk (Nick Rothwell)
Organization: LFCS Enya Admiration Society
Lines: 22
In-reply-to: eberard@ajpo.sei.cmu.edu (Edward Berard)

In article <16836@isvax.isl.melco.co.jp>, eberard@ajpo (Edward Berard) writes:
>What I will attempt to do in this message is to provide you with a
>better understanding of the recursive/parallel life-cycle.
>
>Unfortunately, simple descriptions such as "analyze a little, design a
>little, implement a little, and test a little," are often more
>confusing than they are enlightening. In addition, there is a strong
>tendency to confuse the recursive/parallel life-cycle with rapid
>prototyping approaches (e.g., [Boehm, 1986]). This message is an
>attempt to reduce, if not eliminate, this confusion.

Why is your "recursive/parallel" life-cycle idea tied to
object-oriented languages? I use the same approach when programming in
ML, except that (i) my "objects" don't usually have state, and (ii)
there's no inheritance mechanism. I think that everything else you
mention in your article pretty much carries through.

		Nick.
Nick Rothwell,	Laboratory for Foundations of Computer Science, Edinburgh.
		nick@lfcs.ed.ac.uk    <Atlantic Ocean>!mcvax!ukc!lfcs!nick
~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~
  "...all these moments... will be lost in time... like tears in rain."