Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!unmvax!pprg.unm.edu!topgun.dspo.gov!lanl!opus!ted
From: ted@nmsu.edu (Ted Dunning)
Newsgroups: comp.sw.components
Subject: Re: Common Lisp
Message-ID: 
Date: 29 Sep 89 15:53:35 GMT
References:  <6630@hubcap.clemson.edu>
Sender: news@nmsu.edu
Organization: NMSU Computer Science
Lines: 32
In-reply-to: billwolf%hazel.cs.clemson.edu@hubcap.clemson.edu's message of 29 Sep 89 01:01:15 GMT


i think we are closing in on bill wolfe's problem:

In article <6630@hubcap.clemson.edu> billwolf%hazel.cs.clemson.edu@hubcap.clemson.edu (William Thomas Wolfe, 2847 ) writes:


      By the way, Ted Dunning said earlier regarding Lisp: "if you want to 
      play, grab a copy of one of the pd interepreters".  I will be quite 
      happy to consider anything that will help attain the objectives of 
      the software engineering philosophy, and Common Lisp may well be 
      useful in that respect.  But engineers don't play; this is left 
      for hackers.  We're here to engineer products on time, under budget,
      and with as much quality as we can get within those two constraints.



playing with something new is a wonderful way to find out it's
strengths and weaknesses.  programming etudes to explore the
capabilities of tools without necessarily producing something that
people will sell is just as important as etudes and scales are to the
player of musical instruments.

if you never have time to do anything other than produce code, then
you will (already have?) wind up woefully ignorant of everything
outside your own specialty.

i would hope that the `software engineering philosophy' does not
preclude self-education.
--
ted@nmsu.edu
			remember, when extensions and subsets are outlawed,
			only outlaws will have extensions or subsets