If you pronounce (+ 2 3) as "the sum of two and three" rather than "plus two three", it makes much more sense.
Follow me for more tips like this.
If you pronounce (+ 2 3) as "the sum of two and three" rather than "plus two three", it makes much more sense.
Follow me for more tips like this.
@PaniczGodek Thought you said #Lisp, how is it related to #Clojure or #Scheme? :blobsweats:
@jackdaniel I know, that is sorta the very subtle point.
The arguments what is more Lisp, or less or if hygienic macros are better than non-hygienic , if pure functional is better than imperative, ITERATE vs LOOP vs DOTIMES vs DO ... recursive ..
It is all bullshit, sometimes the hammer is the best screwdriver but you lack it, you cannot solve your problem.
@amszmidt @PaniczGodek name gatekeeping did more harm than good to lisp community, just saying.
@jackdaniel It is not, in any sense of the word. You cannot run a trivial (Common, Zeta, MAC, Inter ...) Lisp program in Scheme. The semantics are plenty different that I think, truly, that it is useful and even important to differentiate Scheme and Lisp (which is different from one being better or worse .. they are both nice languages!)
I sometimes troll that PHP is a C since .. for many trivial programs, you need to change less than between Scheme and Lisp.
@amszmidt @PaniczGodek such disputes are silly and I like Common Lisp better than others, but "a lisp" refers to many languages and I'd wager an opinion that Common Lisp is closer semantically and functionally to r6rs than LISP 1.5
@amszmidt right, so the difference is that while in Lisp and Scheme you'd pronounce (* 2 3) as "the product of two and three", in Clojure you'd rather say "projuct"
as a schemer, I tried reading both Maclisp and Interlisp, and my experience is that I find Maclisp fairly understandable (and relatively close in spirit to Scheme), whereas I couldn't understand almost anything from Interlisp, and their spirits felt far apart.
In the incidental interview I made a year ago with Bernard Greenberg (who wrote Multics Emacs in Maclisp, after all), he called Scheme "Sussman and Steele’s much-improved Lisp"
@PaniczGodek @weekend_editor @amszmidt
DO is a syntactic sugar for tail recursion. I've even made a short blog post about it:
https://turtleware.eu/posts/How-do-you-DO-when-you-do-DO.html
Good question
I think that Norvig's PAIP code is generally good (although IMO it's nicer when rewritten to Scheme), but I find CLOS-heavy code more difficult to digest.
I find that Common Lisp in general has some 'ancient' vibe, which I don't necessarily like. I much prefer Scheme's recursive functions, named let and map/filter/append-map to CL's loop macro, dolist etc.
(Scheme also has the CL-like "do" syntax that I don't understand, and don't want to understand)
There are some things though that are tragic in Scheme (like records and modules) thar are at least acceptable in Common Lisp.
@PaniczGodek @amszmidt @jackdaniel
How are you with reading Common Lisp?
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.