Live data from Hacker News

Common Lisp Implementations in 2023

n16f.net

41–50 of 243 posts

Re: Common Lisp Implementations in 2023

#41
post #29

ECL license is LGPL-2.1-or-later (not LGPL2), the same applies to Clasp (which was forked from ECL). n.b isn't this thread infested with bots? 4 or 5 nicks created 4 days ago with incomplete messages..

Indeed, corrected. Thank you! I'm not sure what is happening, there are multiple small posts which look like spam, with green nicknames. Edit: green nicknames are from new accounts. On this page, all of them are spam. At some point it would make sense to just hide them all.

the correction is not really correct - you say lgpl-2.1 without the "or later version". It is sometimes abbreviated ls LGPL-2.1+, but SPDX identifier is preferable since it is semi-standard for abbreviating license names.

Re: Common Lisp Implementations in 2023

#44
post #38
post #37

Earlier quoted context omitted.

What do you mean by "open [...] in a new REPL"? You use ASDF:LOAD-SYSTEM to have ASDF load all the content of the system, making it available to you.

I edited the comment to add some additional details. Am I not supposed to load or compile the contents of an `.asd` file?

No you do not have to. ASDF knows where to find your ASD files:

https://asdf.common-lisp.dev/asdf.html#Configuring-ASDF-to-f...

Personally I use the (:tree (:home "dev/lisp")) form.

Post reply on HN