>>> Yes, it's confusing, and I'm very much against it. Interpretation of ELisp
>>> code (even compiled code) now changes in a very subtle manner depending on
>>> whether a record named `hash-table` happens to be defined or not.
SM> Similarly, interpretation of Elisp code can change in a very subtle
SM> manner if someone does (fset 'apply (lambda ...)).
> OK, but the read behavior is more broken. Right now records have
> basicall taken over all #s
No, only those that are not taken by other uses.
Stefan