From: Mark H Weaver <mhw@netris.org>
To: John Cowan <cowan@ccil.org>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: Self-evaluating function and closure
Date: Sat, 15 Jun 2019 20:39:31 -0400 [thread overview]
Message-ID: <878su24b35.fsf@netris.org> (raw)
In-Reply-To: <CAD2gp_S=Q5dnnjWJNRTVk2PU6UVp8PybEcMh9QRptRqhoy6sYw@mail.gmail.com> (John Cowan's message of "Sat, 15 Jun 2019 15:35:47 -0400")
Hi John,
John Cowan <cowan@ccil.org> writes:
> On Sat, Jun 15, 2019 at 4:31 AM Vladimir Zhbanov <vzhbanov@gmail.com> wrote:
>
> The result is unexpected for me, I expected a new self-evaluating
>> procedure every time I run the function-generator procedure (and
>> it works differently with Guile 2.0, IIUC, cannot check just now).
>>
>
> I tested this on Chicken, Biwa, and Chbi, and all agree on producing new
> closures that are not eq?. So I'd call it a bug in either Guile or
> the Scheme standard, but probably in Guile.
I don't understand your reasoning. If you think it's a bug in Guile,
can you cite a specific requirement in a relevant Scheme standard that
we are violating here?
I also don't know why you would call it a bug in the Scheme standard.
Can you explain why you think this?
Mark
next prev parent reply other threads:[~2019-06-16 0:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 20:29 Self-evaluating function and closure Vladimir Zhbanov
2019-06-15 19:35 ` John Cowan
2019-06-16 0:39 ` Mark H Weaver [this message]
2019-06-16 0:36 ` Mark H Weaver
2019-06-16 9:02 ` Vladimir Zhbanov
2019-06-16 10:09 ` Mark H Weaver
2019-06-17 8:03 ` Vladimir Zhbanov
2019-06-16 9:47 ` Mark H Weaver
2019-06-16 10:21 ` Thomas Morley
2019-06-16 10:32 ` Mark H Weaver
2019-06-16 10:42 ` Thomas Morley
2019-06-16 11:29 ` Mark H Weaver
2019-06-17 8:48 ` Vladimir Zhbanov
2019-06-17 14:21 ` Mark H Weaver
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=878su24b35.fsf@netris.org \
--to=mhw@netris.org \
--cc=cowan@ccil.org \
--cc=guile-user@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).