In Common Lisp, both flet and labels make lexical bindings of slightly different sorts: flet is a special form for local function binding. Bindings are not recursive and cannot refer to each other. Each binding contains function name, arguments, and function body. labels is a special form for local function binding. Bindings can be recursive … Read more
Making hello.exe: * (defun main () (print “hello”)) MAIN * (sb-ext:save-lisp-and-die “hello.exe” :toplevel #’main :executable t) [undoing binding stack and other enclosing state… done] [saving current Lisp image into hello.exe: writing 3160 bytes from the read-only space at 0x22000000 writing 2592 bytes from the static space at 0x22100000 writing 30134272 bytes from the dynamic space … Read more
SLIME’s contrib directory seems to have SWANK implementations for MIT Scheme and Kawa.
Characters for return and linefeed \r is the character #\return in Common Lisp. \n is the character #\linefeed in Common Lisp. The following ends the string “Hello world.” with return and linefeed. (format t “Hello world.~C~C” #\return #\linefeed) #\newline is whatever the platform uses as a line division. On Unix machines this is often the … Read more
Wikipedia and the Google Common Lisp Style guide both suggest .lisp. Practical Common Lisp suggests .lisp or .cl. Note, I’m not a Common Lisp programmer by any measure, so I have no idea if .lisp is actually used in practice.
It means that your program code you write is also data which can be manipulated by a program. Take a simple Scheme expression like (+ 3 (* 6 7)) You can regard it as a mathematical expression which when evaluated yields a value. But it is also a list containing three elements, namely +, 3 … Read more
I haven’t looked at it recently, but at least in the past there were some problems with fully implementing common lisp on the CLR, and I’d be a little surprised if this has changed. The issues come up with things like the handling of floats where .net/clr has a way to do it that is … Read more
What’s going on? You say: feel like there is nothing special is going on here. The outer foo in bar increments the global x, and foo surrounded by let in bar increments the shadowed x. What’s the big deal? The special that’s going on here is that LET can shadow the value of *x*. With … Read more
You have several answers here, but none is really comprehensive (and I’m not talking about having enough details or being long enough). First of all, the bottom line: you should not use Common Lisp if you want to have a good experience with SICP. If you don’t know much Common Lisp, then just take it … Read more
DEFPARAMETER always assigns a value. So: [1]> (defparameter a 1) A [2]> (defparameter a 2) A [3]> a 2 while DEFVAR does it only once, so: [4]> (defvar b 1) B [5]> (defvar b 2) B [6]> b 1 SETF is a macro which uses SETQ internally, but has more possibilities. In a way it’s … Read more