Marko Rauhamaa <ma...@pacujo.net>: > I don't see any practical reason for that limitation. If you allow > setq/setf/set!, you have no reason to disallow symbol-value on a local > variable.
In fact, the reason probably is practical and analogous to the locals() caveat in Python. If the language made local variables available indirectly, I'm guessing some optimizations would be much harder or impossible. In my own lisp implementation, where performance is not a concern at all, the local variables are both lexically scoped and offer access to symbol-value. Marko -- https://mail.python.org/mailman/listinfo/python-list
