From: ludovic.courtes@laas.fr (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Per-module reader, take #3
Date: Thu, 17 Nov 2005 11:03:46 +0100 [thread overview]
Message-ID: <87psoz8ubh.fsf@laas.fr> (raw)
In-Reply-To: <87zmo4jny6.fsf@ossau.uklinux.net> (Neil Jerram's message of "Wed, 16 Nov 2005 21:13:37 +0000")
Neil Jerram <neil@ossau.uklinux.net> writes:
> I still don't like the module option (no surprise there), and I think
> that the other parts of the patch could be made a bit simpler (which
> to my mind is a Good Thing). To be completely concrete about what I
> mean, here is a version of your patch which I prefer (untested except
> by make check). Please let me know what you think.
It seems equally acceptable to me. Originally, I decided to not expose
the `current-reader' fluid in order to be consistent with other
"stealthy" uses of fluids, like `current-module' (the fluid itself is
not exported, only a setter and a getter are). But this has the
drawback of requiring the `dynamic-wind' hair in `basic-load'. And it
also looks more mysterious or magic to user, which is not a good thing.
So either way will be fine to me.
Thanks!
Ludovic.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-11-17 10:03 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 12:51 [PATCH] Per-module reader Ludovic Courtès
2005-09-26 12:29 ` Ludovic Courtès
2005-09-26 22:55 ` Kevin Ryde
2005-09-27 9:04 ` Ludovic Courtès
2005-09-26 19:05 ` Neil Jerram
2005-09-27 8:21 ` Ludovic Courtès
2005-10-11 11:26 ` Ludovic Courtès
2005-10-11 23:24 ` Neil Jerram
2005-10-12 9:11 ` Ludovic Courtès
2005-10-17 9:17 ` [PATCH] Per-module reader, take #2 Ludovic Courtès
2005-10-17 20:41 ` Neil Jerram
2005-10-18 7:42 ` Ludovic Courtès
2005-10-19 22:23 ` Neil Jerram
2005-10-20 1:22 ` Kevin Ryde
2005-10-20 7:59 ` Ludovic Courtès
2005-10-20 19:30 ` Kevin Ryde
2005-10-20 21:27 ` Neil Jerram
2005-10-20 7:48 ` Ludovic Courtès
2005-10-20 10:52 ` Tomas Zerolo
2005-10-20 14:42 ` Ludovic Courtès
2005-10-20 22:09 ` Neil Jerram
2005-10-21 7:43 ` Ludovic Courtès
2005-10-24 11:43 ` Ludovic Courtès
2005-10-28 21:26 ` Neil Jerram
2005-10-28 22:38 ` Kevin Ryde
2005-10-29 8:58 ` Neil Jerram
2005-10-30 19:55 ` Neil Jerram
2005-11-07 16:06 ` [PATCH] Per-module reader, take #3 Ludovic Courtès
2005-11-16 21:13 ` Neil Jerram
2005-11-17 10:03 ` Ludovic Courtès [this message]
2005-11-20 0:15 ` Marius Vollmer
2005-11-21 12:55 ` Ludovic Courtès
2005-12-03 20:02 ` Neil Jerram
2005-12-05 8:31 ` Ludovic Courtès
2005-12-07 0:04 ` Marius Vollmer
2005-12-14 1:00 ` Neil Jerram
2005-12-14 14:06 ` Ludovic Courtès
2005-12-14 19:37 ` Neil Jerram
2005-12-15 9:13 ` Ludovic Courtès
2005-12-15 19:47 ` Neil Jerram
2005-12-16 6:13 ` Tomas Zerolo
2005-12-16 8:32 ` Neil Jerram
2005-12-16 9:21 ` Tomas Zerolo
2005-12-16 8:55 ` Ludovic Courtès
2005-12-17 10:26 ` Neil Jerram
2005-12-17 13:09 ` Marius Vollmer
2005-12-29 10:27 ` Neil Jerram
2006-01-11 16:45 ` Ludovic Courtès
2006-01-13 17:38 ` Neil Jerram
2005-10-19 22:56 ` [PATCH] Per-module reader Neil Jerram
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=87psoz8ubh.fsf@laas.fr \
--to=ludovic.courtes@laas.fr \
--cc=guile-devel@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).