LispForum

The signal/slot concept in Qt appeared because of C++ limitations (lack of GC and lack of first-class functions). In Common Lisp, it is more idiomatic to implement events (analogous to events in .Net and signals in Gtk+). Basically an event is a list (or array) of functions (or weak pointers to func...

Slime and its backends have implementations of single-step debugging.

I was just wondered what others, in their experience with lisp, have often wanted from read macros and readtables. Are you satisfied with what one can do with them now in the current standard or do you wish for something more? :? Personally, I would like (1) Readtables per package rather than a glo...

It is much better and simpler to use CL-WHO (http://weitz.de/cl-who/) or CXML (http://common-lisp.net/project/cxml/sax ... ialization) to generate XML.

Ramarren wrote:KILL-WORD takes an argument. Emacs is self-documenting, if you are unsure how to use a function use 'C-h f', which by default is bound to describe-function command.

Or, better, enable the `eldoc-mode' that will show description of function under cursor in the minibuffer.

subhuman wrote:seems as if debian isn't much lisp-a-lized, is it? i'll have to install cl-gtk2 manually. anyway, many thx for the links.

The only Lisp-friendly Linux distributive is Gentoo at the moment. Usually, Gentoo contains latest versions of most Lisp libraries.

But I think the bigger point that the article made, is that PicoLisp is Truer to the core purpose and value of the Lisp programming language, a language that is supposed to always and everywhere be directly programmable in itself, a physical embodiment of the lambda calculus. If large parts of the ...

I skimmed the article, and, to be honest, it is ignorant and/or insane. The author doesn't seem to know what 'compilation' even means. I mean, CLisp is used as an example of a compiler. The quoted fragment alone shows total ignorance of type inference and optimization. It seems to be pushing Pico L...

I played only a little with assembly, but as far as I know you just mark a heap region as executable if necessary, depending on your operating system (see NX bit on Wikipedia, mprotect syscall on Linux) and jump to it. Of course you need an assembler to generate the machine code which can be placed...

Although not required by standard, CL implementations usually implement tail call optimization. E.g., SBCL, clisp (as a compiler, not interpreter), ecl (as a compiler).