From: Andreas Rottmann <a.rottmann@gmx.at>
To: Andy Wingo <wingo@pobox.com>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: @ and @@ in r6rs libs [Was: R6RS exception printing at the REPL]
Date: Mon, 29 Nov 2010 23:35:27 +0100 [thread overview]
Message-ID: <8762vfvjv4.fsf@delenn.lan> (raw)
In-Reply-To: <m3hbezzy20.fsf_-_@unquote.localdomain> (Andy Wingo's message of "Mon, 29 Nov 2010 21:15:19 +0100")
Andy Wingo <wingo@pobox.com> writes:
> On Sat 27 Nov 2010 01:08, Andreas Rottmann <a.rottmann@gmx.at> writes:
>
>> [ It's off-topic in this thread, but I think the circular dependencies
>> introduced by using `@' and `@@' in the R6RS modules should at one
>> point be eliminated; they work almost all the time, but can fail in
>> surprising ways -- see the commit comment of c0f6c163... ]
>
> Agreed, FWIW; to the extent that it's possible anyway. For me it's also
> fine to have auxiliary modules in the rnrs namespace, if needed to break
> cycles.
>
I'll look into this when I have some extranous time on my hands; I think
`(rnrs private ...)' seems like a decent choice for modules internal to
the R6RS implementation, although I'm of course open to suggestions.
Regards, Rotty
--
Andreas Rottmann -- <http://rotty.yi.org/>
next prev parent reply other threads:[~2010-11-29 22:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-24 21:46 R6RS exception printing at the REPL Andreas Rottmann
2010-11-20 15:23 ` Andy Wingo
2010-11-20 18:18 ` Andreas Rottmann
2010-11-20 20:19 ` Andy Wingo
2010-11-27 0:08 ` Andreas Rottmann
2010-11-29 20:15 ` @ and @@ in r6rs libs [Was: R6RS exception printing at the REPL] Andy Wingo
2010-11-29 22:35 ` Andreas Rottmann [this message]
2010-11-29 20:34 ` R6RS exception printing at the REPL Andy Wingo
2010-11-29 23:20 ` Andreas Rottmann
2010-12-01 23:16 ` Ludovic Courtès
2010-12-01 23:13 ` Ludovic Courtès
2010-12-02 20:21 ` Andreas Rottmann
2010-12-13 16:49 ` 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=8762vfvjv4.fsf@delenn.lan \
--to=a.rottmann@gmx.at \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/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).