comp.lang.ada
 help / color / mirror / Atom feed
From: djsalomon@watdaisy.UUCP (Daniel J. Salomon)
Subject: Re: Thus spake the DoD...
Date: Wed, 27-Feb-85 14:22:55 EST	[thread overview]
Date: Wed Feb 27 14:22:55 1985
Message-ID: <7016@watdaisy.UUCP> (raw)
In-Reply-To: 3223@utah-cs.UUCP

> The way we say it around here is "most programs written in *other* languages
> could be written better in Lisp" - that includes work in VLSI, graphics,
> compilers, algebra, and suchlike.  Name me ONE thing that Pascal or Ada
> does better than Lisp (besides `confuse and frustrate the programmer')...
> 
> 							stan shebs

Since LISP is a typeless language a LISP interpreter or compiler will
accept almost any meaningless input (in which the parentheses match)
as a valid program.  Thus the correctness of programs must be proved by
exhaustive test cases or by theoretical analysis.  Although LISP is
more amenable to theoretical analysis than most languages, let's face
it, most LISP programmers would rather hack out another test case than
do any analysis.

Since LISP uses function notation for all operations it is a simple
language to implement and a simple language in which to automatically
generate code (thus the AI connection).  Similarly its use of lists to
implement all data types and all structures is a simple and interesting
concept.  But these two features have made LISP one of the most
inefficient languages in existence.  In many ways this inefficiency
has hindered the development of AI.  People now associate AI with
programs that are too costly to run.

This inefficiency has led LISP programmers on an endless search for
more powerful hardware.  The search may lead to new and exciting
parallel architectures but until they are designed and built we should
find ways to make good use of the hardware we have.

Writing in LISP is challenging and fun.  It's simplicity both liberates
and constrains the programmer so that writing LISP programs is
something like solving a puzzle or playing chess.  Many intelligent
people enjoy this aspect of LISP.  Unfortunately LISP programs remain a
puzzle even after they are written.  LISP programs are both
syntactically and logically hard to document.  Usually only the
original author will fully understand how a LISP program works, and
after a few years not even he will.

I thus stand by my original claim that the importance of LISP to AI is
greatly exaggerated.  Not only can one now chose one of the LISP
offspring such as PROLOG or FORTH, but also if one is writing an actual
production system one should examine one of the more efficient
algorithmic languages to see if it is adequate for one's application.

  reply	other threads:[~1985-02-27 19:22 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1985-02-14 15:59 Thus spake the DoD Frederick J Dickey
1985-02-17  1:58 ` Robert Hofkin
1985-02-17 16:36 ` g-frank
1985-02-18  5:18   ` Skef Wholey
1985-02-18 14:33 ` Chuck Hedrick
1985-02-19 19:09   ` Daniel J. Salomon
1985-02-22  2:21     ` LISP &c (re: the DoD...) Thomas M. Breuel
1985-02-25 17:08     ` Thus spake the DoD Jan Steinman
1985-02-26 23:20     ` Stanley Shebs
1985-02-27 19:22       ` Daniel J. Salomon [this message]
1985-03-01 19:30         ` Stanley Shebs
1985-03-01 20:13         ` neves
1985-03-02  4:33         ` Thomas M. Breuel
1985-03-02 18:35           ` Efficiency of LISP Marty Sasaki
1985-03-03  0:23         ` Language criticism Greg Davidson
1985-03-06 14:13         ` Thus spake the DoD geb
1985-02-28  3:16       ` David Schachter
1985-03-01 19:00         ` Stanley Shebs
1985-03-03  3:08         ` Joaquim Martillo
1985-03-03  6:12         ` T J Jardine
1985-03-05 16:55           ` Jan Steinman
1985-03-05 21:07           ` Robert A. Pease
1985-03-12  1:47           ` Ed Colbert
1985-03-13 19:35       ` Monique M Taylor
1985-03-17 19:49         ` Jan Steinman
1985-03-21  1:17           ` faustus
1985-03-12  0:25     ` Efficiency of LISP Stavros Macrakis
1985-03-12  2:11     ` Efficiency of numerical Lisp code (details) Stavros Macrakis
1985-03-13  7:05     ` Chuck Hedrick
1985-03-13 20:00     ` Speed with numbers: PDP-10 Maclisp vs. Fortran (details) Stavros Macrakis
1985-03-14 10:12       ` Tim Maroney
1985-03-15  0:27         ` Bill Henneman
1985-03-16  0:59           ` Tim Maroney
1985-03-17 18:58             ` Bill Henneman
1985-03-18  5:02               ` Multi-language systems Marty Sasaki
1985-03-20 17:01                 ` Tom Slack
1985-03-18 21:24               ` Speed with numbers: PDP-10 Maclisp vs. Fortran (details) Tim Maroney
1985-03-19  6:45                 ` Fortran better than Lisp for numerical code? Barry Margolin
1985-03-19 17:35                   ` Speed of Lisp numerical code Stavros Macrakis
1985-03-20 21:04                   ` Fortran better than Lisp for numerical code? T J Jardine
1985-03-22  2:10                     ` Joe Orost
1985-03-19 16:15                 ` Speed with numbers: PDP-10 Maclisp vs. Fortran (details) Bill Henneman
1985-03-19  3:40               ` Norman Diamond
1985-03-18  3:01             ` Common Lisp and Arrays Joaquim Martillo
1985-02-18 23:49 ` Thus spake the DoD M.Fischer
1985-03-14 20:50 ` Speed with numbers: PDP-10 Maclisp vs. Fortran (details) Stavros Macrakis
1985-03-15 15:42 ` Stanley Shebs
  -- strict thread matches above, loose matches on Subject: below --
1985-02-15 14:34 Thus spake the DoD Frederick J Dickey
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox