unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: "Göran Weinholt" <goran@weinholt.se>
To: 31864@debbugs.gnu.org
Subject: bug#31864: Hex-escaped r6rs symbols are not read correctly
Date: Sat, 16 Jun 2018 23:04:39 +0200	[thread overview]
Message-ID: <87k1qy30k8.fsf@teapot.weinholt.se> (raw)

Hello schemers!

R6RS specifies an inline hex escape syntax for symbols. These do not
work in Guile 2.2.3:

scheme@(guile-user)> (read-enable 'r6rs-hex-escapes)
$1 = (square-brackets r6rs-hex-escapes keywords #f positions)
scheme@(guile-user)> (symbol->string '\x7c;
)
$2 = "\\x7c"

I expected this to return "|".

While fixing this, perhaps it would also be possible to add recognition
of #!r6rs to set the appropriate per-port read options, similarly to how
#!fold-case is recognized? It would make it much easier to load R6RS
code in Guile.

Best Regards,

-- 
Göran Weinholt
Debian developer
73 de SA6CJK





                 reply	other threads:[~2018-06-16 21:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k1qy30k8.fsf@teapot.weinholt.se \
    --to=goran@weinholt.se \
    --cc=31864@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).