Re: eval use ?
- From: Majorinc, Kazimir <false@xxxxxxxxx>
- Date: Tue, 28 Feb 2006 15:35:03 +0100
In article <l2qdd3-4q2.ln1@xxxxxxxxxxxxxxxxxxxxxxxxxxx>,
boldyrev+nospam@xxxxxxxxxxxxxxxxxxxx says...
On 9397 day of my life Majorinc wrote:
Code=data is the single most important idea of Lisp and EVAL is
what make it possible.
My point of view is just opposit. To resolve conflict, we should
define Lisp first :)
McCarthy seems to be on my side:
"It seems to me that LISP will probably be superseded for many
purposes by a language that does to LISP what LISP does to
machine language. Namely it will be a higher level language
than LISP that, like LISP and machine language, can refer to
its own programs."
Perhaps, your statement (second part: "and EVAL is ...") is true for
original Lisp, but Lisp is evolving, and it is not true for Common
Lisp.
How do you think "code=data" can be possible without EVAL?
Macros fall short here, because code=data means that code can
be processed during runtime, just like data is usually
processed during runtime.
Lisp can exist without macros and closures, but without EVAL it is
not Lisp any more.
Perl has eval too (and many other `scripting' languages do). So
does perl have Lisp nature?
Phrase "Lisp nature" is to vague here.
.
- Follow-Ups:
- Re: eval use ?
- From: josephoswaldgg@xxxxxxxxxxx
- Re: eval use ?
- From: jayessay
- Re: eval use ?
- From: Pascal Costanza
- Re: eval use ?
- References:
- eval use ?
- From: newbie
- Re: eval use ?
- From: Majorinc , Kazimir
- Re: eval use ?
- From: M Jared Finder
- Re: eval use ?
- From: Majorinc , Kazimir
- Re: eval use ?
- From: Ivan Boldyrev
- eval use ?
- Prev by Date: threading
- Next by Date: Re: eval use ?
- Previous by thread: Re: eval use ?
- Next by thread: Re: eval use ?
- Index(es):
Relevant Pages
|