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."
|