unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 14164@debbugs.gnu.org
Subject: bug#14164: letrec: detect illegal accesses to vars before entering body
Date: Fri, 12 Apr 2013 10:43:08 +0200	[thread overview]
Message-ID: <87ppy09m1v.fsf@gnu.org> (raw)
In-Reply-To: <87li8qbuv3.fsf@tines.lan> (Mark H. Weaver's message of "Wed, 10 Apr 2013 05:25:20 -0400")

Mark H Weaver <mhw@netris.org> skribis:

>  @lisp
>  (letrec ((a 42)
> -         (b (+ a 10)))
> +         (b (+ a 10)))  ;; Illegal access
>    (* a b))

Please change it to “invalid access”.  Nothing illegal here.  ;-)

Ludo’.





      reply	other threads:[~2013-04-12  8:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09  4:41 bug#14164: 'letrec' allows to refer to the values of previously bound variables Nikita Karetnikov
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 [this message]

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=87ppy09m1v.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=14164@debbugs.gnu.org \
    --cc=mhw@netris.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).