5 ms·
Feature expressions shouldn't be used in normal applications, only in portability libraries. To use threads on any implementation which supports them (given it'
by jackdaniel 9y ago
Feature expressions shouldn't be used in normal applications, only in portability libraries. To use threads on any implementation which supports them (given it's supported by the recommended portability layer):
> (ql:quickload 'bordeaux-threads)
> (bt:make-thread (lambda () (sleep 1) (print "hijack")))
that's all, no feature expressions whatsoever. Quicklisp is a system manager (something similar to npm in sense that it helps you to download dependencies).
Regarding best libraries: isn't that true for any language? Newbie doesn't know good libraries, because he is a newbie. He has to learn which libraries are good and which are bad.
edit: and by each supported implementation I mean in fact all active complete Common Lisp implementations: ArmedBear, Allegro, clisp, Clozure, Corman, Embeddable, Man-Kai, LispWorks, Steel-Bank and Scieener.
- pjmlp 9y agoI kind of agree with you, however the beauty of a language standard is being the point of reference for libraries and language semantics. In any case, the Lisp like languages I use aren't Common Lisp (Clojure, Emacs Lisp, Script-Fu), so that was just an idea.
- moomin 9y agoI think the point is you can't really have it both ways. CL prides itself on its extensive and portable standard library, but has huge gaps by the standards of modern languages.
- flavio81 9y ago> but has huge gaps by the standards of modern language Please detail, because i'm sure that the Lisp community would love to fill those gaps. After all, Lisp is addictive to the point of resembling a hard drug.
- moomin 9y agoWell, start with the stuff that OP's just been arguing doesn't need a standard implementation. :)