[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Eval - Pro's and Con's (was Re: Dylan rather than CL -- why?)
- To: Stuart Watt <S.N.K.Watt@open.ac.uk>, email@example.com
- Subject: RE: Eval - Pro's and Con's (was Re: Dylan rather than CL -- why?)
- From: Jeff Dalton <firstname.lastname@example.org>
- Date: Tue, 8 Dec 92 14:08:08 GMT
- In-reply-to: Stuart Watt's message of 8 Dec 92 11:01:26 U
> There is a big issue hovering below the surface here. eval is used for
> REP loops, and REP loops are part of things like "command-line" interfaces,
> but not usually anything to do with GUIs. I wouldn't want to see eval put
> in to help develop the wrong kind of system.
What? EVAL just does the eval part. It's READ and PRINT that are
the "wrong kind" of interface.
However, one of the key advantages of Lisp is that there's a defined
external representation for a wide range of data object. One of the
things that keeps me from using other languages is that I usually
have to write a bunch of tedious I/O routines before I can try things
This is not to say that READ and PRINT should be delivered in
applications though, or that they're useful in every case.
However, their usefulness is not confined to "command-line"