News for hackers. Stuff that matters.

A comment on Modern, functional Common Lisp: myths and best practices.

Re:Modern, functional Common Lisp: myths and best practices by pjmlp on Tuesday February 25, 2020 @07:19AM (#22412544)
Very nice overview, I failed to see references to LispWorks and Allegro, though.
[ Parent | on HN ]
Re:Modern, functional Common Lisp: myths and best practices by rgrau on Tuesday February 25, 2020 @08:55AM (#22413175)
One little thing I did for Allegro was to compile their docs into a dash docset so you can use emacs' dash-docs with it.

- https://github.com/kidd/AllegroLisp.docset

- https://github.com/dash-docs-el/

[ Parent | on HN ]
Re:Modern, functional Common Lisp: myths and best practices by TurboHaskal on Tuesday February 25, 2020 @07:22AM (#22412567)
Which is a pity because at least for LispWorks, the IDE itself and the CAPI GUI toolkit could be considered killer apps.
[ Parent | on HN ]
Re:Modern, functional Common Lisp: myths and best practices by Ambrevar on Tuesday February 25, 2020 @07:58AM (#22412783)
I've never used them myself, so in all honesty I have nothing to say about them! :p

That said, I support free software and I believe a proprietary compiler is not a good idea :(

[ Parent | on HN ]
Re:Modern, functional Common Lisp: myths and best practices by TurboHaskal on Tuesday February 25, 2020 @08:37AM (#22413038)
Ideology aside, most proprietary compilers (mostly for Forth, Pascal and Lisp) I have used are of _excellent_ quality.

A lot also provide you the source code once you pay. AllegroCL is one of them I think.

[ Parent | on HN ]
Re:Modern, functional Common Lisp: myths and best practices by pjmlp on Tuesday February 25, 2020 @08:27AM (#22412980)
The FOSS experience is a poor imitation of Lisp Machines.
[ Parent | on HN ]