From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] `try-module-autoload' and `current-reader'
Date: Fri, 20 Jan 2006 08:54:23 +1100 [thread overview]
Message-ID: <87acdrsx2o.fsf@zip.com.au> (raw)
In-Reply-To: <87irshhy65.fsf@ossau.uklinux.net> (Neil Jerram's message of "Thu, 19 Jan 2006 00:13:54 +0000")
Neil Jerram <neil@ossau.uklinux.net> writes:
>
> it is occasionally useful for a backtrace to show that module X
> is being loaded because of code from module Y.
Yes, I've wrestled with that on some inadvertently circular autoloads.
I ended up using %load-hook to show what was actually happening
though.
> 2. Interpreting a file path beginning with "." as relative to the
> current module's load filename.
I've been meaning to add something to the docs on how load is relative
to the current file (unless you use "./"). A carry-over from emacs or
something I suppose.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-01-19 21:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 9:06 [PATCH] `try-module-autoload' and `current-reader' Ludovic Courtès
2006-01-19 0:13 ` Neil Jerram
2006-01-19 8:42 ` Ludovic Courtès
2006-01-21 8:46 ` Neil Jerram
2006-01-23 8:22 ` Ludovic Courtès
2006-01-26 19:25 ` Neil Jerram
2006-01-27 8:41 ` Ludovic Courtès
2006-02-04 15:54 ` Neil Jerram
2006-01-19 21:54 ` Kevin Ryde [this message]
2006-01-20 8:31 ` Ludovic Courtès
2006-01-20 20:47 ` Kevin Ryde
2006-01-21 8:29 ` 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=87acdrsx2o.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).