References: CLtL p.354, pp.51-2
Edit history: 29-Apr-90, Version 1 by Moon (for Steele)
The issues passed on the character proposal did not explicitly address
the following, but they no longer make sense in light of the new
character scheme that has been adopted.
The #nnn\x reader syntax creates a character with font attribute nnn,
but there is no longer a font attribute.
COERCE coerces an integer to a character by calling INT-CHAR, but the
INT-CHAR function no longer exists.
This is Symbolics issue #26.
Remove the #nnn\x reader syntax; an implementation can define it as an
Remove coercion from integer to character.
Presumably the character subcommittee simply overlooked these points and
the above proposal would have passed with the other character proposals
if it had been proposed.
I don't know.
Cost to Implementors:
Cost to Users:
Cost of non-adoption:
These two features will still be in the language, but their specification
will not make any sense.