LispForum

(eval (read)) evaluates (read) and not '(a b) Unless you are using some eval I am not familiar with, then this is wrong. EVAL is a function, so first its argument is evaluated (if this is circular evaluator, then it might be by the same EVAL function), resulting in '(a b), which is the shorthand fo...

The specifications specifically prohibits macros expanding into declarations: http://www.lispworks.com/documentation/HyperSpec/Body/s_declar.htm Macro forms cannot expand into declarations; declare expressions must appear as actual subexpressions of the form to which they refer. I think this is beca...

The purpose of array types is to allow implementation to use specialized memory layout for the array. The specification allows the type to be upgraded to most specific such type (see http://www.lispworks.com/documentation/HyperSpec/Body/f_upgr_1.htm ). In the case of custom types no specialized layo...

Lispworks documentation has a chapter about timers: http://www.lispworks.com/documentation/lw51/LWUG/html/lwuser-234.htm . I don't use Lispworks, but this might be what you want. In general I doubt that generating interrupts from FFI code is a good idea, but this obviously depends on the implementat...

REDRAW is not exported from ltk-mw package. In any case using USE-PACKAGE in code is bad practice, you create your own package with DEFPACKAGE and add use declarations there. Also, REQUIRE is not portable, or rather, the way it works (in SBCL it just goes through ASDF) is not. Creating asd file with...

As for speed it doesn't matter really because most time is spent in SDL which is written in C anyway. Same goes for OpenGL. If you are writing a game bound by graphics, then yes, but it not impossible to write a game which requires a lot of processing. Especially since games are usually soft real t...

First, note that Lisp is actually a family of very different languages, most important being Common Lisp, Scheme and Emacs Lisp, and lots of specialized dialects, like the one Naught Dog used. Also, Clojure recently appeared, which is a very interesting Lisp running on Java virtual machine. And what...

The example of when the difference matters which I ran into a few times are configuration variables, which have some default values, but which you might want to change from the REPL when developing/testing the program. Since in CL, as findinglisp has written, you can recompile code without restartin...

Custom cores => NOT easily solved. Well, I suppose if considered for end user deployment or something... but even then, compared to installing SBCL at all, it is easy. Just create a file make-utility-core.lisp, (cl:in-package :cl-user) (when (probe-file "sbcl-utility") (delete-file "sbcl-utility"))...

But the --script option breaks some things becacuse it prevents site-init (/etc/sbclrc) and user-init (~/.sbclrc) from being loaded. E.g., on Gentoo using it breaks asdf. This problem is easily solved by using as #! a custom core, with initfiles already loaded. It seems a good idea anyway to avoid ...