From: Nikita Karetnikov <nikita@karetnikov.org>
To: 14164@debbugs.gnu.org
Subject: bug#14164: 'letrec' allows to refer to the values of previously bound variables
Date: Tue, 09 Apr 2013 08:41:04 +0400 [thread overview]
Message-ID: <877gkcuxi7.fsf@karetnikov.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 317 bytes --]
According to the manual [1], this snippet:
(letrec ((a 42)
(b (+ a 10)))
(* a b))
should return "Error: unbound variable: a." But it returns 2184 in
Guile 2.0.7. Either there is a bug in the manual or 'letrec' doesn't
work properly.
[1] https://gnu.org/software/guile/manual/guile.html#Local-Bindings
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next reply other threads:[~2013-04-09 4:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 4:41 Nikita Karetnikov [this message]
2013-04-09 5:14 ` bug#14164: letrec: detect illegal accesses to vars before entering body Mark H Weaver
2013-04-09 6:37 ` Nikita Karetnikov
2013-04-09 16:44 ` Mark H Weaver
2013-04-09 17:22 ` Nikita Karetnikov
2013-04-10 9:25 ` Mark H Weaver
2013-04-12 8:43 ` Ludovic Courtès
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=877gkcuxi7.fsf@karetnikov.org \
--to=nikita@karetnikov.org \
--cc=14164@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).