* bug#33057: Guile's reader assumes the port encoding is ASCII-compatible
@ 2018-10-16 1:42 Mark H Weaver
0 siblings, 0 replies; only message in thread
From: Mark H Weaver @ 2018-10-16 1:42 UTC (permalink / raw)
To: 33057
In several places, Guile's reader assumes that the port encoding is
ASCII-compatible. For example:
* 'scm_token' reads raw bytes and passes them to the CHAR_IS_DELIMITER
macro to check for delimiters.
* 'scm_read_mixed_case_symbol' checks for the (optional) postfix keyword
syntax by comparing the final _byte_ read by 'read_token' with ':'.
* 'scm_read_character' uses 'read_token' to read raw bytes up to the
next delimiter, and if it returns a single byte with value 0-127, it
is interpreted as the associated ASCII character regardless of the
encoding.
* 'scm_read_semicolon_comment' reads bytes until it finds one equal to
the ASCII code for '\n'.
There may be other problems as well.
Mark
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-10-16 1:42 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-10-16 1:42 bug#33057: Guile's reader assumes the port encoding is ASCII-compatible Mark H Weaver
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).