Re:Swift LispKit
by eadmund on Monday May 07, 2018 @10:09PM
(#17018287)
> LispKit is based on the R7RS standard for Scheme.
I think that it should be called SchemeKit, since it's based on Scheme rather than Lisp.
It does look pretty neat. It's extremely odd that lists are immutable (but cons cells are mutable — are lists not conses‽), but maybe that's okay in the Scheme world nowadays?
Edit: LispPad[0] is a really interesting-looking Scheme IDE from the same author.
Re:Swift LispKit
by lispm on Tuesday May 08, 2018 @03:37PM
(#17024092)
Call it only Lisp, if it is actually compatible with Lisp. Otherwise you will confuse people. Scheme compatible languages usually have Scheme in their name (if at all): MitScheme, Macscheme, Chicken Scheme, DRScheme, ...
Re:Swift LispKit
by lispm on Tuesday May 08, 2018 @11:29PM
(#17027239)
It means somehow compatible with the Lisp 1.5 implementtion. Which is an interpreter/compiler, and a base library. It's the first widely used Lisp implementation. This implies cons cell based lists, s-expressions, and a whole bunch of basic control structures and facilities. The first Scheme dialects were quite similar to that, but deviated and extended this in their own direction with a series of language standards RNRS.
If a langage is a Scheme dialect, call it Scheme.
Basic rule: use the nearest (!) language name, one is compatible with. This strives to be a R7RS Scheme. Thus name it Schwme. Then the Scheme literature and the Scheme source libraries apply. If it is a Scheme, I would best get myself a Scheme tutorial to learn using it - reading the Lisp literature is of less direct help.
For example typically Common Lisp implementations have 'Common Lisp' or 'CL' its name, and are not called SchemeSomething. SBCL, CCL, GCl, Allegro Cl, MCL, ECL, ... Exceptions are CLISP or the product LispWorks.
To avoid confusion a language should call itself Lisp, when it is practically (syntactically) a Lisp, not just in the unspecified family of 'Lisp': Logo, Scheme, Clojure, MDL, Dylan, SKILL, ...
Re:Swift LispKit
by garmaine on Wednesday May 09, 2018 @02:06AM
(#17027706)
Scheme most certainly is a Lisp. I agree that the OP should have called it SchemeKit or some such, but I would not agree on a categorization that excludes schemes from the category of “Lisp”.
I think that it should be called SchemeKit, since it's based on Scheme rather than Lisp.
It does look pretty neat. It's extremely odd that lists are immutable (but cons cells are mutable — are lists not conses‽), but maybe that's okay in the Scheme world nowadays?
Edit: LispPad[0] is a really interesting-looking Scheme IDE from the same author.
0: http://lisppad.objecthub.net/
See http://community.schemewiki.org/?scheme-faq-standards#implem...
There are also already Lisp and Scheme implementations called Lispkit...
People generally refer to “Lisp”, unqualified, as referring to the family of languages inclusive of all of the above.
If a langage is a Scheme dialect, call it Scheme.
Basic rule: use the nearest (!) language name, one is compatible with. This strives to be a R7RS Scheme. Thus name it Schwme. Then the Scheme literature and the Scheme source libraries apply. If it is a Scheme, I would best get myself a Scheme tutorial to learn using it - reading the Lisp literature is of less direct help.
For example typically Common Lisp implementations have 'Common Lisp' or 'CL' its name, and are not called SchemeSomething. SBCL, CCL, GCl, Allegro Cl, MCL, ECL, ... Exceptions are CLISP or the product LispWorks.
To avoid confusion a language should call itself Lisp, when it is practically (syntactically) a Lisp, not just in the unspecified family of 'Lisp': Logo, Scheme, Clojure, MDL, Dylan, SKILL, ...