I think the wording in the Guile manual is unfortunate.
What RnRS says is that an identifier which is bound to a location is a
variable.
What the Guile manual is then discussing is our implementation details of
this, where "bound" is used in a different sense than in RnRS.
Den tors 14 nov. 2024
(My current e-mail client keeps corrupting guile-devel@gnu.org and refuses
access to the contact list, please ignore wrong address)
>there are various use-cases where one wants to export a symbol [sic] from a
>module without binding [sic] any value to it in the module where it is being
>exporte
> I think Guile could report a warning if a nonexistent variable is
> exported as the cause of this kind of errors may be difficult to find in
> a large program.
you are exporting _symbols_ (unique identities) from modules, not variables (or
bindings).
there are various use-cases where one want
Thanks!
Maxime Devos kirjoitti 5.11.2024 klo 11.23:
I’ve send it to bug-guile, should appear in the issue tracker soon
--
Kotisivu / Homepage:http://www.iki.fi/tohoyn/
Sähköposti / E-Mail:tommi.hoynalan...@iki.fi
GPG-sormenjälki / GPG fingerprint:
55F4 2477 7155 3528 5CB2 2B7A BB86 1FDE 4046
#74210
I’ve send it to bug-guile, should appear in the issue tracker soon
Here is another example:
--- mod1.scm ---
(define-module (mod1))
(export myproc)
(define (myproc0)
(display "Hello\n"))
--- end ---
--- mod2.scm ---
(define-module (mod2))
(export myproc2)
(use-modules (mod1))
(define (myproc2)
(display "Hello again\n"))
--- end ---
--- program.scm -
>I think Guile could report a warning if a nonexistent variable is
>exported as the cause of this kind of errors may be difficult to find in
>a large program.
During compilation, code is analysed and IIRC there is a warning for unbound
variables. (I don’t know if warning is the default though.)
