home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.lisp
- Path: sparky!uunet!elroy.jpl.nasa.gov!ames!agate!stanford.edu!rock!concert!sas!mozart.unx.sas.com!sasmsr
- From: sasmsr@zinfande.unx.sas.com (Mark S. Riggle)
- Subject: Re: Why Isn't Lisp a Mainstream Language?
- Originator: sasmsr@zinfande.unx.sas.com
- Sender: news@unx.sas.com (Noter of Newsworthy Events)
- Message-ID: <C19snx.2IF@unx.sas.com>
- Date: Fri, 22 Jan 1993 19:26:20 GMT
- References: <1993Jan21.230642.18561@netlabs.com> <19930122162651.0.SWM@SUMMER.SCRC.Symbolics.COM>
- Nntp-Posting-Host: zinfande.unx.sas.com
- Organization: SAS Institute Inc. Cary NC
- Lines: 35
-
-
-
- I think that one aspect of Lisp syntax that can be
- confusing to lisp novices is that the first
- position of a list is the functional call, EXCEPT
- in certain forms. Like the lambda argument list,
- 'let', 'do' and others, including some user defined
- macros.
-
- ie. te consider the following fragments:
-
- (let
- ((fred (x))
- (sam (y))))
-
- (letter
- ((fred (x))
- (sam (y))))
-
- So syntactically they look the same, but we all
- know they are semantically vastly different, except
- of course we have made a macro definition for
- letter that is the same as say let or let*.
-
- I think it actually takes quite some exposure to
- Lisp before this semantic transformation is natural
- and automatic to someone.
-
- --
- =============================================================
- Mark Riggle [Professional Lisp Bigot]
- sasmsr@unx.sas.com
- SAS Institute Inc.,
- SAS Campus Drive, Cary, NC, 27513
- (919) 677-8000
-