[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lisp performance was Re: problems with lisp

To: <address@hidden>
Subject: Re: lisp performance was Re: problems with lisp
From: "Kevin Kelleher" <address@hidden>
Date: Tue, 2 Sep 2003 08:07:27 -0400 (EDT)
Cc: <address@hidden>, <address@hidden>
Importance: Normal
In-reply-to: <3F534BDF.7020404@comcast.net>
References: <m3ad9psg43.fsf@javamonkey.com> <3F534BDF.7020404@comcast.net>
Reply-to: address@hidden
Sender: address@hidden


Vadim Nasardinov said:
>
>    To iterate is illiterate.
>    To recurse is worse.
>    To avoid this trap, see
>    Instructions for MAPC.
>
> Does anyone know who wrote this originally?


By Googling, I found this:

    http://www.cis.upenn.edu/~bcpierce/types/archives/1989/msg00043.html

In which Vaughn Pratt claims authorship, citing his "article on LISP in
Encyclopedia of Computer Sciences and Technology, vol. 10, (ed. Belzer
et al), 1978."

-- 
Kevin Kelleher <kkell@znet.com>

References:
- Re: lisp performance was Re: problems with lisp
  - From: Peter Seibel <peter@javamonkey.com>
- Re: lisp performance was Re: problems with lisp
  - From: Vadim Nasardinov <el-vadimo@comcast.net>

Prev by Date: Re: OO should break when broken
Next by Date: Re: OO should break when broken (was re: the benefits of immutability)
Previous by thread: Re: lisp performance was Re: problems with lisp
Next by thread: Re: lisp performance was Re: problems with lisp
Index(es):
- Date
- Thread