home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!uwm.edu!biosci!agate!stanford.edu!lucid.com!karoshi!york
- From: york@oakland-hills.lucid.com (Bill York)
- Newsgroups: comp.lang.lisp
- Subject: Re: Lisp syntax beauty? (was Re: Why Isn't Lisp a Mainstream Language?)
- Message-ID: <YORK.93Jan25113647@oakland-hills.lucid.com>
- Date: 25 Jan 93 19:36:47 GMT
- References: <dfs.727723285@noonian> <1jpi0sINN47q@elroy.jpl.nasa.gov>
- <dfs.727732459@kehleyr> <1jqgecINNjbf@elroy.jpl.nasa.gov>
- Sender: usenet@lucid.com
- Reply-To: York@Lucid.COM
- Organization: Lucid, Inc.
- Lines: 17
- In-Reply-To: gat@forsight2.jpl.nasa.gov's message of 23 Jan 1993 04:09:48 GMT
-
- In article <1jqgecINNjbf@elroy.jpl.nasa.gov> gat@forsight2.jpl.nasa.gov (Erann Gat) writes:
-
- There is an ongoing discussion on comp.lang.lisp.mcl which might be of
- interest to followers of this thread. The discussion centers on the issue
- of how to produce small applications using Lisp. The suggestion has been
- made that Common Lisp should be considered an operating system and not
- an application. In that case, having a zillion obscure functions is no
- more unreasonable than having a large C library. (BTW - MCL (Macintosh
- Common Lisp) implements all of CLTL2 and is 1.5 Megabytes, about a tenth
- the size of Allegro.)
-
- Actually, the true beauty of the suggestion was the part where you
- take the entire Lisp application, call it an extension (apologies to
- the non-Mac-fluent) and have people drop it in the System Folder.
- After all, it isn't much bigger than Quicktime. Then you disguise the
- fasl files as "applications" and sit back while everyone marvels at
- the compact-but-powerful programs! And they can inter-operate, too!
-