From: Ian Price <ianprice90@googlemail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-user@gnu.org
Subject: Re: Guildhall users: please update your GUILE_LOAD_PATH or %load-path
Date: Sat, 02 Feb 2013 08:34:29 +0000 [thread overview]
Message-ID: <87y5f7f71m.fsf@Kagami.home> (raw)
In-Reply-To: <87pq0mi3fo.fsf@tines.lan> (Mark H. Weaver's message of "Wed, 30 Jan 2013 19:47:23 -0500")
Mark H Weaver <mhw@netris.org> writes:
> In the future it will be important for Guildhall modules to have a lower
> priority than in the search path than Guile's core modules. The reason
> is that Guildhall has several portable SRFIs, some of which will be
> superceded by efficient native implementations in core Guile. One such
> example is SRFI-41, which will soon be replaced by a superior version in
> Guile core.
Not just SRFIs, who knows what other packages will end up bundled with
Guile in the future. However, I do ideally want to see modules in the
Guildhall first, and this change allows this.
> Ian, can you please update your Guildhall "Getting-Started" document
> appropriately? <https://github.com/ijp/guildhall/wiki/Getting-Started>
I have updated the page accordingly.
--
Ian Price -- shift-reset.com
"Programming is like pinball. The reward for doing it well is
the opportunity to do it again" - from "The Wizardy Compiled"
prev parent reply other threads:[~2013-02-02 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 0:47 Guildhall users: please update your GUILE_LOAD_PATH or %load-path Mark H Weaver
2013-02-02 8:34 ` Ian Price [this message]
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=87y5f7f71m.fsf@Kagami.home \
--to=ianprice90@googlemail.com \
--cc=guile-user@gnu.org \
--cc=mhw@netris.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).