Re: Patch: Promoting characters to 31 bits (for discussion)
Hrvoje Niksic <hniksic(a)srce.hr> writes:
"William M. Perry" <wmperry(a)aventail.com> writes:
> It also uses it to make 'dingbats' characters, and only ever uses
> that on things like ?j ?i, etc, which are safe. If (make-char ...)
> can take something other than an int,
You misunderstand. `make-char' is kosher. `int-char' is not, and
neither is `char-int'. (Except in internal code, or if you really know
what you're doing.)
I have to make the letter 'j' in a funky character set that I define, and
the table I make them from has real chars in it because ?j is easier to
read, and make-char will not take a char as an argument.
Why do you need int-char and char-int in SOCKS?
Because I like to write things that will be reasonably sane looking like
(if (= (char-int x) 5)
...
)
instead of
(if (= ?\005 x)
...
)
At least, that looks better to me. :)
-Bill P.