From: rain1@openmailbox.org
To: guile-devel@gnu.org
Subject: include bug in guile
Date: Tue, 29 Mar 2016 18:16:44 +0100 [thread overview]
Message-ID: <314fdd510b24fc4580a47e0da868d3ba@openmailbox.org> (raw)
I think this is a bug in guile relating to "include":
a.scm: (define a 1)
b.scm: (include "a.scm") (display a) (newline)
guile -l b.scm # prints 1
now update
a.scm: (define a 2)
guile -l b.scm # still prints 1
next reply other threads:[~2016-03-29 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 17:16 rain1 [this message]
2016-03-30 1:05 ` include bug in guile Wette, Matthew R (3441)
2016-03-31 12:39 ` Wette, Matthew R (3441)
2016-03-31 12:55 ` rain1
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=314fdd510b24fc4580a47e0da868d3ba@openmailbox.org \
--to=rain1@openmailbox.org \
--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).