From: Peter Lane <peter@peterlane.info>
To: kawa@sourceware.org
Subject: Re: import path vs CLASSPATH
Date: Mon, 13 Feb 2017 19:31:00 -0000 [thread overview]
Message-ID: <ab0bdfca-c31e-24c4-28df-c8ee8b1f88f1@peterlane.info> (raw)
In-Reply-To: <b46ed793-f972-e31e-5e87-935e29c7eace@bothner.com>
On 08/02/17 21:41, Per Bothner wrote:
> Depends what you mean by "the program". The path is relative to the
> *importing* module.
> I.e. the source file that contains the import or require form.
Yes, this makes more sense now. It is quite logical, although I did get
caught out even after looking at the manual - by thinking the
import.path was analogous to CLASSPATH.
> Perhaps changing "If the resulting filename is relative, then it is
> resolved relative to the current root."
> adding ", which is derived from the name of the source file containing
> the import/require"
> might make it clearer?
That would help make things clearer. I also think the point should be
flagged up earlier - the third paragraph could include a similar phrase:
"Each path element is combined ... to produce a filename; relative path
elements are /relative to the source file containing the import/require/."
--
Peter Lane
http://peterlane.info/scheme.html
prev parent reply other threads:[~2017-02-13 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 18:37 Peter Lane
2017-02-08 21:42 ` Per Bothner
2017-02-13 19:31 ` Peter Lane [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ab0bdfca-c31e-24c4-28df-c8ee8b1f88f1@peterlane.info \
--to=peter@peterlane.info \
--cc=kawa@sourceware.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).