Re: XEmacs and char representation in blowfish.el
"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
>>>>> "Simon" == Simon Josefsson
<jas(a)extundo.com> writes:
Simon> ?\xCAFE to work in the core could be useful in itself, and
No, it's more trouble than it's worth; this is precisely what we call
"Ebola" in the code. Anyway, XEmacs already has a perfectly good
hexadecimal notation for integers: #xCAFE. Rationale: it's standard,
even Common:
http://www-2.cs.cmu.edu/Groups/AI/html/hyperspec/HyperSpec/Body/sec_2-4-8...
Nice, this sounds like the correct solution. OK, I have sent a patch
for blowfish that use the new syntax to xemacs-patches. The only
problem is that it doesn't work on Emacs, but this is probably a
non-problem and will even be fixed once the elisp parser in Emacs
understands ?#xCAFE. Thanks.
Simon> translate into the hex integer 4E03. Declaring a
character
Simon> using its hex code seems like nonsense,
What about http://www.unicode.org/Public/UNIDATA/? It _will_ make
sense to resurrect this notation in the near future, for precisely
that purpose. However, the reader will signal on code points that are
not assigned characters.
IMHO this should use a different syntax. Maybe ?\U4711 or something.