From: Klaus Stehle <klaus.stehle@uni-tuebingen.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 11198@debbugs.gnu.org, Klaus Stehle <klaus.stehle@uni-tuebingen.de>
Subject: bug#11198: problems reading data with a "read-hash-extend" registered reader
Date: Wed, 11 Apr 2012 21:07:43 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.61.1204112043460.5742@commlink.zdv.uni-tuebingen.de> (raw)
In-Reply-To: <87zkaka9xl.fsf@gnu.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1233 bytes --]
On Mon, 9 Apr 2012, Ludovic Courtès wrote:
> Date: Mon, 09 Apr 2012 23:10:14 +0200
> From: Ludovic Courtès <ludo@gnu.org>
> To: Klaus Stehle <klaus.stehle@uni-tuebingen.de>
> Cc: 11198@debbugs.gnu.org
> Subject: Re: bug#11198: problems reading data with a "read-hash-extend"
> registered reader
>
> Hi Klaus,
>
> Klaus Stehle <klaus.stehle@uni-tuebingen.de> skribis:
>
> > (read-hash-extend #\R read-R)
>
> Unlike previous versions, Guile 2.0 has distinct compilation and
> run-time phases. Here you probably want the reader extension to become
> effective at compile-time (when compiling), and at evaluation-time (when
> interpreting the code):
>
> (eval-when (compile eval)
> (read-hash-extend #\R read-R))
>
> There’s an example of this in the manual, in the context of
> ‘current-reader’ (info "(guile) Loading").
>
> Does it work for you?
>
> Thanks,
> Ludo’.
>
Hallo Ludo’,
No it doesn't work. The same behavour: the script runs with a compiler
error message but nevertheless the record is created and displayed
correctly.
The only way to run the script without error message is to run it with
the --no-auto-compile option.
Thanks,
Klaus
next prev parent reply other threads:[~2012-04-11 19:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-07 20:16 bug#11198: problems reading data with a "read-hash-extend" registered reader Klaus Stehle
2012-04-09 21:10 ` Ludovic Courtès
2012-04-11 19:07 ` Klaus Stehle [this message]
2012-04-11 19:33 ` Mark H Weaver
2012-04-11 20:34 ` Klaus Stehle
2012-04-22 13:43 ` Mark H Weaver
2012-04-22 18:01 ` Ludovic Courtès
2012-04-24 8:11 ` Andy Wingo
2012-04-24 11:24 ` Noah Lavine
2012-04-24 11:38 ` Noah Lavine
2012-04-24 16:22 ` Ludovic Courtès
2012-07-05 8:00 ` bug#11198: prefab structs in guile Andy Wingo
[not found] ` <877gui7i3y.fsf@pobox.com>
2012-07-05 20:57 ` Ludovic Courtès
[not found] ` <87ipe2dizn.fsf@gnu.org>
2012-07-05 21:06 ` Andy Wingo
[not found] ` <878vex534f.fsf@pobox.com>
2012-07-05 21:55 ` Ludovic Courtès
[not found] ` <874npldga9.fsf@gnu.org>
2012-07-05 22:03 ` Andy Wingo
2012-07-05 22:06 ` Andy Wingo
[not found] ` <87ipe13lya.fsf@pobox.com>
2012-07-05 22:14 ` Ludovic Courtès
[not found] ` <87a9zdc0tc.fsf@gnu.org>
2012-11-27 21:52 ` Ludovic Courtès
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=Pine.LNX.4.61.1204112043460.5742@commlink.zdv.uni-tuebingen.de \
--to=klaus.stehle@uni-tuebingen.de \
--cc=11198@debbugs.gnu.org \
--cc=ludo@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).