From: Evan Prodromou <evan@glug.org>
Subject: Re: letrec bug ?!? with guile-1.5.4
Date: Fri, 22 Mar 2002 11:19:09 -0600 [thread overview]
Message-ID: <87pu1wo702.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us> (raw)
In-Reply-To: <8D1414482878D4119AEE00508B6C9074089662B8@seacex02.eib.electrabel.be> (Sebastien.deMentendeHorne@electrabel.com's message of "Thu, 21 Mar 2002 18:17:54 +0100")
>>>>> "Sd" == Sebastien deMentendeHorne <Sebastien.deMentendeHorne@electrabel.com> writes:
Sd> Hi, What a strange behaviour for guile-1.5.4 on a Mandrake 8.1
Sd> system
Sd> (letrec ((a 2) (b (* a 4))) (display b)) => unbound variable a
Sd> when evaluating arguments of * in (* a 4)
I think what you want to do here is a (let*), not a (letrec).
~ESP
--
Evan Prodromou
evan@glug.org
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2002-03-22 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 17:17 letrec bug ?!? with guile-1.5.4 Sebastien.deMentendeHorne
2002-03-21 17:50 ` Joshua Judson Rosen
2002-03-22 17:19 ` Evan Prodromou [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=87pu1wo702.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us \
--to=evan@glug.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).