From: Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: top-repl priority of guile module
Date: Sat, 30 Dec 2006 23:34:57 +0000 [thread overview]
Message-ID: <871wmhj6u6.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <871wn2hyy8.fsf@zip.com.au> (Kevin Ryde's message of "Fri, 15 Dec 2006 09:53:03 +1100")
Kevin Ryde <user42@zip.com.au> writes:
> Neil Jerram <neil@ossau.uklinux.net> writes:
>>
>> It seems to me, though, that this is all a matter of ordering, not of
>> whether the duplicates processing gets invoked.
>
> I thought that too, until just fiddling with the order didn't fix
> srfi-17 (which #:replace's car and friends).
>
>> I don't know all the details of the duplicate processing,
OK, I understand all this now; thanks for being patient for me. (The
effect of #:replace is that the module with the #:replace always win
over another module that doesn't, regardless of ordering.)
>> And then the real problem, as I understand it, would be that the code
>> in script.c generates code which does the (use-modules (srfi srfi-1))
>> before the (top-repl).
>
> Alas of course top-repl doesn't return ...
Indeed. Still, if it would help we could easily make script.c pass in
unevaluated code to top-repl, which top-repl would eval after the
existing module-uses. However, as you say ...
> top-repl only adds some friendly extras like ice-9 debug, session,
> regexp and threads. Hopefully they don't overlap with any srfis, so
> it shouldn't matter if they're after use-srfis. If that sounds right.
Yes, agreed. The (module-use ... 'guile) was a more serious problem
here, but now it is gone (which I agree is a good fix). So no new
script.c hackery is needed.
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-12-30 23:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 21:59 top-repl priority of guile module Kevin Ryde
2006-12-04 12:15 ` Ludovic Courtès
2006-12-05 0:26 ` Kevin Ryde
2006-12-05 3:15 ` Kevin Ryde
2006-12-05 9:53 ` Ludovic Courtès
2006-12-08 21:23 ` Kevin Ryde
2006-12-08 21:31 ` Kevin Ryde
2006-12-14 20:05 ` Neil Jerram
2006-12-14 22:53 ` Kevin Ryde
2006-12-30 23:34 ` Neil Jerram [this message]
2006-12-15 8:32 ` Ludovic Courtès
2006-12-30 23:37 ` Neil Jerram
2007-01-01 22:44 ` Kevin Ryde
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=871wmhj6u6.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
/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).