3 ms·
I'm not sure calling "Clojure not a lisp, but partially derived from it" really makes sense. That code from other lisp implementations needs rewritten to be po
by taeric 11y ago
I'm not sure calling "Clojure not a lisp, but partially derived from it" really makes sense.
That code from other lisp implementations needs rewritten to be ported, is really not that much different from how many other lisp implementations were to each other.
CL and Scheme did a lot to unify things, such that any scheme should run another scheme's code. Same for any CL implementation. But, for example, running emacs lisp in any other lisp just isn't going to work.
- lispm 11y agoWell, actually Emacs Lisp and Common Lisp were derived from the same language and share a lot. CL-USER> (defun fact (n) (do* ((i n (- i 1)) (j i (* j i))) ((= i 1) j))) FACT CL-USER> (fact 15) 1307674368000 Unchanged code in Elisp... ELISP> (defun fact (n) (do* ((i n (- i 1)) (j i (* j i))) ((= i 1) j))) fact ELISP> (fact 15) 1307674368000 (#o23016735654000, #x13077775800) Elisp originally was designed as a Maclisp subset. Common Lisp was designed as a Maclisp successor.
- taeric 11y agoFair. There have been, and always will be lisps that can be copy pasted between each other. Just as you can get some implementations of programs in some assemblies that work between assemblies. That does not say anything about whether or not a language is an assembly. Just as this says nothing about whether a language is a lisp.
- lispm 11y agoA family is a social construct. It's about sharing, communicating, learning, building, inheritance. Emacs Lisp is directly in the tradition of McCarthy's Lisp. It shares names, concepts, literature, even code. Logo, Dylan, ML, Clojure don't. They were derived or inspired by Lisp, but they are now they own language family...
- 59nadir 11y agoYou're bunching Clojure in with several languages that have strayed far further from Lisp. Clojure was designed specifically with the intent of being a dialect of Lisp, which means it's explicitly not in its own language family or in any other language family than Lisp.
- lispm 11y ago> Clojure was designed specifically with the intent of being a dialect of Lisp The result of that design is that Clojure shares literally zero lines of code with other Lisps: Autolisp, ISLisp, Emacs Lisp, Standard Lisp, Common Lisp. Many basic concepts are absent, renamed or redesigned ('Atom', 'Linked List', ...). Clojure is fully incompatible to any other language with Lisp in its name. Programs have to be re-architectured, because the concepts are different: no TCO, but 'functional', different approach about side effects (-> avoid), lazy persistent datastructure at its core, different idea of OOP (-> avoid), Lisp infrastructure (-> avoid), ... There is no software I know of, which is shared. The number of tools shared is 'one': GNU Emacs. It's a different community with different goals, different software, different applications, different libraries. Just think of it: zero lines of code is shared. My problem with that broader idea of 'Lisp': it is fully vague and it has no practical implications. Sometimes it's only a marketing slogan. It has the same vague meaning like 'object-oriented' or 'Functional'. There is no consensus what OOP in a broad sense means and how it should be defined. 'Lisp' is just as useless. It does not mean that Clojure is useless or worse than Lisp. Totally not. Clojure has new ideas on data structures put to work and enabled some very productive people enjoying their tools. They are doing wonderful stuff.
- calibraxis 11y agoSome people (including someone who worked on the CL standard) opined Scheme is not a Lisp: https://groups.google.com/forum/#!topic/comp.lang.lisp/Bj8Hx6mZEYI[1-25] https://groups.google.com/forum/#!topic/comp.lang.lisp/Bj8Hx... In any discussion involving Common Lisp, there will be the opinion that "Clojure is not a Lisp" without (in my view) providing sufficient context for this clearly confusing statement. (FWIW, I call Clojure a Lisp. It is clearly in the Lisp tradition, not to mention more technical things like: code-is-data, serious REPL, accurate numbers like 10.00000000000000001M. I don't think "Lisp" should be reserved for mainly incremental improvements on an old movement.)
- lispm 11y ago> Code-is-data, serious REPL, accurate numbers Like Prolog or Julia.
- deleted 11y ago[deleted]
- calibraxis 11y agoThat’s not a quote. You capitalized "Code-is-data" as if it were starting its own sentence. Had you quoted the whole sentence, your response would've seemed more like a non-sequitur. In any case, there is no definition of even "chair". (Which partitions the world into chair and not-chair. Simply imagine a continuum between a particular chair morphing into a not-chair; where exactly does it stop being a chair?) So I'm unconcerned about edge-cases, where a language is actually in a fuzzy part of that continuum. Not to mention those amusing blogposts claiming "Javascript is a Lisp!" which maybe aren't objectively true but inspiring.
- pygy_ 11y agoJulia is arguably a Lisp too. Add first class functions to the mix.
- hvis 11y agoOther Lisp dialects, not implementations. Common Lisp has "implementations", Scheme has "implementations". The word "implementation" implies a high degree of compatibility. But there are a lot of languages in the Lisp family that don't share the syntax (except from the basics, maybe), nor the standard libraries. See e.g. http://blog.fogus.me/2011/05/03/the-german-school-of-lisp-2/ http://blog.fogus.me/2011/05/03/the-german-school-of-lisp-2/