LispForum

I appreciate the clarity, since my comment was intended to make the same point you're making about side effects. If you want something to "stick" in the FASL then you can't rely on side effects that don't stick across Lisp instances. Unlike you, I'm doing this on a laptop with Clozure CL, ...

Well, if you're using intern in the macro, that's already a side effect. So make-package is just one more side effect. It's like you said—if you need to make a defconstant form, then you can't do that without having a symbol at macro-expansion time. I came up with this macro for illustrative purpo...

(2 3 3) isn't a pair. You mean any list of numbers?

Answered elsewhere: http://forums.autodesk.com/t5/visual-li ... -p/6668181

Relevant documentation: https://projects.ncsu.edu/project/graph ... snap1.html

I don't use Qt myself, but this guy has done a lot of work with it: http://shinmera.github.io/qtools/

In the definition and initial value form for *operadores*, it looks like it's wanting to call the LIST function, but the outer form is quoted, not evaluated.

Each element of the association list is a list, so you want 'f' to be some element of that list—the second element, I guess? I mean, it's redundant to be mapping each symbol to itself.

Repeatedly printing X and Y doesn't reveal the whole process, whereas explicit nesting might make things clearer. The call (z 4 9) can be re-expressed, via the function definition, as: (inc (z (dec 4) 9)) Evaluating the innermost form, this becomes: (inc (z 3 9)) Rewriting the call to Z, like we did...

Wow, this is already looking fairly complete. It's easy to see this being an alternative to straight C/C++ for complicated simulation work. Embedded systems, too, since with modifications it could even compile to a specialized dialect like nesC , which I recall being kind of tedious to write, for so...

The two lists are structurally different. The keys, in the latter example, are themselves lists. So you'd need to use a different test function in order to compare the keys effectively: