From: Vijay Marupudi <vijaymarupudi@gatech.edu>
To: 49452@debbugs.gnu.org
Subject: bug#49452: Confusing behavior with (include) used in file in GUILE_LOAD_PATH
Date: Tue, 6 Jul 2021 19:31:38 -0500 [thread overview]
Message-ID: <7b37a89f-39a6-1433-daf4-469a40656a6b@gatech.edu> (raw)
Hello all,
It is unclear to me what the intended behavior for (include
"filename.scm") is, so I'm sending an email about this potential bug.
The Local Inclusion docs
<https://www.gnu.org/software/guile/manual/html_node/Local-Inclusion.html>
seem to state that relative paths are found relative to the file that
included them.
> If file-name is a relative path, it is searched for relative to the
> path that contains the file that the include form appears in.
So if I have a file "/libraries/libname/main.scm" than has (include
"./helpers.scm"), then the file "/libraries/libname/helpers.scm"
*should* (I think) be imported.
But this does not seem to work if "/libraries" is in the GUILE_LOAD_PATH
and my current working directory is somewhere else, say "/home/user" and
I'm running "/home/user/program.scm" that imports the (libname main)
library from "/libraries". Then Guile seems to try to include the
"libname/helpers.scm" file from the current directory, which does not
exist.
Conversations with leoprikler in IRC have revealed to me that
call-with-include-port is the function responsible for this behavior
<https://git.savannah.gnu.org/cgit/guile.git/tree/module/ice-9/psyntax.scm#n3231>.
`syntax-source` returns a file path relative to the load path, and
include tries to use that path to open a file relative to the current
working directory.
In Guile's bug guidelines
<https://www.gnu.org/software/guile/docs/docs-2.2/guile-ref/Reporting-Bugs.html>,
to me this fits
* Whenever documentation and actual behavior differ, you have certainly
found a bug, either in the documentation or in the program.
and potentially
* When some part of the documentation is not clear and does not make
sense to you even after re-reading the section, it is a bug.
I believe this is a bug, but I may be wrong, so emailing to clarify.
Thank you!
Vijay Marupudi
PhD Student in Human Centered-Computing
Georgia Institute of Technology
next reply other threads:[~2021-07-07 0:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 0:31 Vijay Marupudi [this message]
2021-07-07 8:29 ` bug#49452: Confusing behavior with (include) used in file in GUILE_LOAD_PATH Taylan Kammer
2021-07-08 11:43 ` Vijay Marupudi
2021-07-07 21:22 ` Bengt Richter
2021-07-09 4:08 ` Vijay Marupudi
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=7b37a89f-39a6-1433-daf4-469a40656a6b@gatech.edu \
--to=vijaymarupudi@gatech.edu \
--cc=49452@debbugs.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).