From: Marco Maggi <marco.maggi-ipsu@poste.it>
To: bug-guile@gnu.org
Subject: [r6rs] #\x0 is a perfectly valid character datum representation
Date: Mon, 21 Jun 2010 10:12:39 +0200 [thread overview]
Message-ID: <8739wg4xe0.fsf@rapitore.luna> (raw)
The following R6RS program:
(import (rnrs))
#\x0
fails with:
;;; note: source file proof.sps
;;; newer than compiled /home/marco/.cache/guile/ccache/2.0-0.R-LE-4/home/marco/var/tmp/proof.sps.go
Backtrace:
In ice-9/boot-9.scm:
170: 10 [catch #t #<catch-closure 96b6610> ...]
In unknown file:
?: 9 [catch-closure]
In ice-9/boot-9.scm:
62: 8 [call-with-prompt prompt0 ...]
In ice-9/eval.scm:
389: 7 [eval # #]
In ice-9/boot-9.scm:
1858: 6 [save-module-excursion #<procedure 9758840 at ice-9/boot-9.scm:1871:3 ()>]
1149: 5 [load "proof.sps" #f]
1051: 4 [%start-stack load-stack ...]
1056: 3 [#<procedure 97587b0 ()>]
In unknown file:
?: 2 [primitive-load "proof.sps"]
In ice-9/boot-9.scm:
115: 1 [#<procedure 95aa2f8 at ice-9/boot-9.scm:109:6 (thrown-k . args)> read-error ...]
In unknown file:
?: 0 [catch-closure read-error "scm_lreadr" ...]
ERROR: In procedure scm_lreadr:
ERROR: proof.sps:5:5: unknown character name x0
on a i686-pc-linux-gnu using commit
8d10ccae79ff46f0ebea92ba36acfaebafba8d86.
It looks like the hex notation for characters is not
recognised by the reader.
--
Marco Maggi
next reply other threads:[~2010-06-21 8:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 8:12 Marco Maggi [this message]
2010-06-21 19:26 ` [r6rs] #\x0 is a perfectly valid character datum representation Andy Wingo
2010-06-21 20:27 ` Mike Gran
2010-06-21 20:36 ` Andy Wingo
2010-06-21 20:42 ` Mike Gran
-- strict thread matches above, loose matches on Subject: below --
2010-07-17 11:22 Mike Gran
2010-07-17 11:38 ` Andy Wingo
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=8739wg4xe0.fsf@rapitore.luna \
--to=marco.maggi-ipsu@poste.it \
--cc=bug-guile@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).