public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Debabrata Pani <debabrata.pani@gmail.com>
To: kawa@sourceware.org
Subject: learning scheme : difference in letrec behavior
Date: Tue, 03 Nov 2015 02:42:00 -0000	[thread overview]
Message-ID: <CAKJw4feinTa1_VA+6r8zVy0uMhWNYe1BNjEzGcUhvrYjXuGTtg@mail.gmail.com> (raw)

In kawa (2.1 , 2.0) ,
the expression and its result

#|kawa:27|# (letrec ((x 1) (y (+ x 2))) (+ y x))
4
#|kawa:28|#

But the above expression fails in chicken/gambit
gsi error message
*** ERROR IN (console)@1.19 -- (Argument 1) NUMBER expected
(+ #!unbound 2)

from my point of view , this is harmless. And probably portability
with other scheme implementations is not my concern as well.

But will this have any other unwarranted impact ?

Regards,
Debabrata Pani

             reply	other threads:[~2015-11-03  2:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03  2:42 Debabrata Pani [this message]
2015-11-03  2:53 ` Per Bothner
2015-11-03  2:55   ` Per Bothner
2015-11-03  4:41     ` Debabrata Pani

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKJw4feinTa1_VA+6r8zVy0uMhWNYe1BNjEzGcUhvrYjXuGTtg@mail.gmail.com \
    --to=debabrata.pani@gmail.com \
    --cc=kawa@sourceware.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).