From: Ian Hulin <ian@hulin.org.uk>
To: guile-devel@gnu.org
Subject: Re: add-relative-load-path ? - scm_add_load_path too?
Date: Mon, 30 Jan 2012 20:20:16 +0000 [thread overview]
Message-ID: <4F26FB80.9040906@hulin.org.uk> (raw)
In-Reply-To: <87zkdycjl6.fsf@pobox.com>
Hi Andy, Ludo,
I've just seen the add-load-path scheme function in the new git
documentation.
Please, please, pretty please can we have a scm_add_load_path API
equivalent callable from C/C++? The LilyPond initialization code
currently does disgusting things like faking
(eval (set! %load-path cons ( <blah> %load-path ) ) )
a call such as
(scm_add_load_path (scm_from_locale_string ("<blah") );
would look far more civilized, and I'd be able to take out the
current hack, complete with the comments containing shudders of disgust.
Cheers,
Ian Hulin
On 08/01/12 15:14, Andy Wingo wrote:
> Hi all,
>
> In the following thread:
>
> http://thread.gmane.org/gmane.lisp.guile.user/8298/focus=8403
>
> there was a concern that it's difficult to set up the load path
> for simple one-off scripts.
>
> I had a proposal that we add something like this:
>
> (define-syntax add-relative-load-path (lambda (x) (syntax-case x
> () ((_ path) (string? (syntax->datum #'path)) (let* ((src
> (syntax-source #'x)) (current-file (or (and src (assq-ref src
> 'filename)) (error "Could not determine current file name")))
> (vicinity (dirname (canonicalize-path current-file))) (path-elt
> (in-vicinity vicinity (syntax->datum #'path)))) #`(eval-when
> (compile load eval) (set! %load-path (cons #,path-elt
> %load-path))))))))
>
> Then in your script you would (add-relative-load-path ".").
>
> Maybe we need an `add-to-load-path' form that handles the
> eval-when, actually, so it would be
>
> (add-to-load-path (dirname (current-source-filename)))
>
> or something like that. (We'd have to define
> current-source-filename as well, in terms of
> current-source-location.)
>
> What do folks think? Is it work it?
>
> Andy
next prev parent reply other threads:[~2012-01-30 20:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-08 15:14 add-relative-load-path ? Andy Wingo
2012-01-14 21:48 ` Neil Jerram
2012-01-20 23:14 ` Andy Wingo
2012-01-21 23:17 ` Neil Jerram
2012-01-23 10:18 ` Andy Wingo
2012-01-23 15:45 ` Ludovic Courtès
2012-01-23 16:20 ` Andy Wingo
2012-01-23 19:36 ` Neil Jerram
2012-01-25 12:42 ` Ludovic Courtès
2012-01-25 14:31 ` Andy Wingo
2012-01-25 20:41 ` Ludovic Courtès
2012-01-25 23:08 ` Andy Wingo
2012-01-23 20:19 ` Neil Jerram
2012-01-30 20:20 ` Ian Hulin [this message]
2012-01-31 8:53 ` add-relative-load-path ? - scm_add_load_path too? Mark H Weaver
2012-01-31 16:10 ` Mark H Weaver
2012-02-01 23:30 ` Ian Hulin
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=4F26FB80.9040906@hulin.org.uk \
--to=ian@hulin.org.uk \
--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).