On Mon, Aug 1, 2011 at 5:32 AM, Matthew Mondor mm_li...@pulsar-zone.netwrote:
I audited the symbol.d and package.d code today, and wrote down some
notes about possible future improvements.
It would be nice if someone did this for the whole of the Hyperspec :-)
Although GENSYM is more often
On Mon, Aug 1, 2011 at 11:43 AM, Matthew Mondor mm_li...@pulsar-zone.netwrote:
So I guess the symbols to rebind would be only the ones which are
likely to be SETQ/SETF via common standard functions rather than via
LET, such as indeed *PACKAGE* (WITH-PACKAGE would not have needed such,
but
On Mon, 1 Aug 2011 14:05:39 +0200
Juan Jose Garcia-Ripoll juanjose.garciarip...@googlemail.com wrote:
Even *PACKAGE* might not need to be thread-local. The place where *package*
is most used is in loaded code, within IN-PACKAGE statements, but LOAD binds
*PACKAGE*, both in binary and in source
On Mon, 01 Aug 2011 07:09:32 -0700
Antony lisp.li...@gmail.com wrote:
the counter is used *only* for the purpose of *naming* the gensyms.
the counter has nothing to with the uniqueness of symbol objects
generated by gensym
the counter does help with symbol names to look distinct but that is
On Mon, Aug 1, 2011 at 8:39 PM, Matthew Mondor mm_li...@pulsar-zone.netwrote:
contrib/defsystem/defsystem.lisp:4019:(setf *package*
package)
contrib/defsystem/defsystem.lisp:4100: (setf *package* (find-package
old-package)))
External package. Probably wrong: they should