News for hackers. Stuff that matters.
Re:Essential Elisp libraries by wglb on Friday April 26, 2013 @11:41AM (#5613514)
quicklisp for lisp libraries is a smashing success.

Personally, I think the problem in the Ruby world is the blazing pace at which folks are producing Ruby stuff.

Re:Essential Elisp libraries by fabriceleal on Friday April 26, 2013 @11:49AM (#5613563)
In ubuntu, when using the packaged clisp and asdf (installable via apt-get), i'm unable to install quicklisp without some hacking around (it complains about the asdf version).

But I agree with you, quicklisp is awesome.

Re:Essential Elisp libraries by wglb on Friday April 26, 2013 @01:25PM (#5614143)
Ok, I never use the host os package manager for certain key things, including Lisp, Ruby. For Lisp, i get from the SBCL site or the proper site (SBCL, Clisp, Clozure CL) I am using. And i compile the source each time. (Obviously to bootstrap you gotta pull the binary the first time). After that, everything is a piece of cake.

I have done less with ruby lately, but as I recall the only way to survive was to use RVM or apparently now chruby to get everythin and compile it up.

Re:Essential Elisp libraries by fabriceleal on Friday April 26, 2013 @01:37PM (#5614238)
> For Lisp, i get from the SBCL site or the proper site (SBCL, Clisp, Clozure CL) I am using

I'll try that approach. Never really tried SBCL or Clozure CL.

> And i compile the source each time

You mean that you compile, for instance, Clisp? I tried to do it once, because FFI usage is dependent of a the flag --with-dynamic-ffi being set in the ./configure step [1][2]. I don't remember exactly why, but I got some difficulties in the build process, but I managed to do it.

This may be a little out of scope, but does anybody know about a common lisp implementation that is more FFI-friendly?

[1]: http://stackoverflow.com/questions/130636/how-to-compile-cli... [2]: http://stackoverflow.com/questions/3901698/is-there-a-way-to...

Re:Essential Elisp libraries by aidenn0 on Friday April 26, 2013 @01:47PM (#5614314)
I heard that clang is now the default C compiler on OS X? clisp can't be built reliably with clang on x86_64 (clisp people on irc thought it was likely a bug in clang).

sbcl doesn't rely on the C compiler so you should have no problems building it on mac OS. Clozure CL was originally a CL specifically for the mac, so it definitely should work fine. SBCL seems to be the most popular open-source implementation, as it can generate extremely good code, often with just minimal type annotations.

Re:Essential Elisp libraries by wglb on Saturday April 27, 2013 @12:38AM (#5616823)
I use sbcl--been a while since I used clisp.

By each time, I mean for updates to sbcl.

Re:Essential Elisp libraries by aerique on Friday April 26, 2013 @04:04PM (#5615113)
On Debian (and possibly Ubuntu) one can get the SBCL package from unstable (it doesn't depend on much) and go from there if installing from source is too much of a hassle.

Don't install any other Common Lisp stuff SBCL doesn't depend on from the Debian repository though, except maybe ASDF. Get everything else through Quicklisp.

Re:Essential Elisp libraries by binarysoul on Friday April 26, 2013 @02:02PM (#5614418)
the problem is also dependencies specified as:

gem 'activesupport', '>= 2.3.5' # too loosely