From: "Wette, Matthew R (3441)" <matthew.r.wette@jpl.nasa.gov>
To: "rain1@openmailbox.org" <rain1@openmailbox.org>
Cc: "guile-devel@gnu.org" <guile-devel@gnu.org>
Subject: Re: include bug in guile
Date: Wed, 30 Mar 2016 01:05:23 +0000 [thread overview]
Message-ID: <7EDD3134-9BE2-4A4F-A8D5-C0617DD17674@jpl.nasa.gov> (raw)
In-Reply-To: <314fdd510b24fc4580a47e0da868d3ba@openmailbox.org>
[-- Attachment #1: Type: text/plain, Size: 702 bytes --]
On Mar 29, 2016, at 10:16 AM, rain1@openmailbox.org<mailto:rain1@openmailbox.org> wrote:
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
I have noticed this behavior and have learned to live with it. Given the following from the Guile Reference manual (2.0.11), I think it is not considered a bug.
"On the other hand, include does have all the disadvantages of early binding: once the code with the include is compiled, no change to the included file is reflected in the future behavior of the including form."
[-- Attachment #2: Type: text/html, Size: 1886 bytes --]
next prev parent reply other threads:[~2016-03-30 1:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 17:16 include bug in guile rain1
2016-03-30 1:05 ` Wette, Matthew R (3441) [this message]
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=7EDD3134-9BE2-4A4F-A8D5-C0617DD17674@jpl.nasa.gov \
--to=matthew.r.wette@jpl.nasa.gov \
--cc=guile-devel@gnu.org \
--cc=rain1@openmailbox.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).