- encoding of it--for example, a Japanese Kanji character might be
- encoded as `^[$(B#&^[(B' using the ISO-2022 encoding
- standard--rather than the numerical representation of the char;
- this way, if the mapping between chars and integers changes, which
- is quite possible for Kanji characters and other extended
- characters, the same character will still be created. Note that
- some primitives confuse chars and integers. The worst culprit is
- `eq', which makes a special exception and considers a char to be
- `eq' to its integer equivalent, even though in no other case are
- objects of two different types `eq'. The reason for this
- monstrosity is compatibility with existing code; the separation of
- char from integer came fairly recently.)
+ encoding of it - for example, a Japanese Kanji character might be
+ encoded as `^[$(B#&^[(B' using the ISO-2022 encoding standard -
+ rather than the numerical representation of the char; this way, if
+ the mapping between chars and integers changes, which is quite
+ possible for Kanji characters and other extended characters, the
+ same character will still be created. Note that some primitives
+ confuse chars and integers. The worst culprit is `eq', which
+ makes a special exception and considers a char to be `eq' to its
+ integer equivalent, even though in no other case are objects of two
+ different types `eq'. The reason for this monstrosity is
+ compatibility with existing code; the separation of char from
+ integer came fairly recently.)