home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!know!hri.com!noc.near.net!news.bbn.com!usc!zaphod.mps.ohio-state.edu!cs.utexas.edu!sun-barr!ames!agate!stanford.edu!rutgers!cmcl2!panix!fhd
- From: fhd@panix.com (Frank Deutschmann)
- Newsgroups: comp.object
- Subject: Apple's Dylan language
- Message-ID: <1992Nov12.235240.19671@panix.com>
- Date: 12 Nov 92 23:52:40 GMT
- Organization: PANIX Public Access Unix, NYC
- Lines: 35
-
-
- While reading through the Apple Dylan manual (_Dylan an Object
- Oriented Dynamic Language_ by Apple Eastern Research and Technology),
- I came accross the following in the Preface by Ike Nassi:
-
- Common Lisp is aimed primarily at the Lisp community, while
- Dylan is accessible to application developers unfamiliar with Lisp.
- Common Lisp is oriented more towards exploratory programming with
- delivery capability, while Dylan is oriented more towards delivery
- with exploratory capability.
-
- Given that Dylan has much in common with Scheme (and therefore Lisp),
- I was wondering about these two statements; as the Apple book is a
- reference manual it merely expounds on the subject of Dylan without
- putting it [the language] into the context of other, similar,
- languages/developmnet systems.
-
- I would like to open a discussion on the relevant merrits of Dylan
- versus Common Lisp (with CLOS), and/or Scheme (but I'm not so familiar
- with Scheme) -- to start with, can anyone provide a basis for the
- above quoted statements? Is Ike Nassi essentially saying that Dylan
- is a smaller system than Common Lisp/CLOS, and therefore easier to
- learn, easier to write better code sooner? Or is the point to say
- that Dylan embodies some fundamental improvement over other Lisp-ish
- environments?
-
- Anyone for comp.lang.dylan?
-
-
-
-
-
- --
- -frank
- (fhd@panix.com)
-