LispForum

So, it turns out making function versions of the stuff I need ain't so bad after all (since I do not mind automatic evaluation of arguments.) Latest version of my closure builder: (defun argpass (control-function &rest inputs) (let ((curried-control control-function) (input-functions ()) (index-...

I hadn't thought about using lazy evaluation in context of differentiating special ops/macros from functions, thanks. Honestly, I am not even sure what you are trying to achieve. What special operator or macro other than possibly AND/OR would you ever want to APPLY? They are syntax abstractions, eve...

Why would it need to involve eval? Obviously I don't know the precise steps involved, but special operators can be called at runtime, so it's just a matter of bindings... so the compiler/intepreter is not build to handle late(r) bindings for special ops? Is that the issue? I don't particularly care ...

My understanding of the compilation/interpretation process is a bit limited, but I don't mind the performance penalty. This is for prototyping only. Hopefully it's possible to function or macro away the complexity. The goal here is expressiveness and ease of use. Someone else suggested wrapping spec...

I know about the (every #'identity mylist) trick to emulate an (apply #'and mylist), but is there a general solution? I'm a bit of a noob, but I think I've managed to construct a lovely little closure builder with only one drawback: (defun functional (this-function &rest other-functions) (lambda...