From: Pierpaolo Bernardi <olopierpa@gmail.com>
To: Damien Mattei <damien.mattei@gmail.com>
Cc: Jeronimo Pellegrini <j_p@aleph0.info>, guile-user <guile-user@gnu.org>
Subject: Re: cond clause does not allow definitions
Date: Thu, 23 May 2024 16:59:05 +0200 [thread overview]
Message-ID: <CANY8u7E=0DE-+a44LnLzsAYf1arTAfdrj_YwGGuUXVaC7tsoog@mail.gmail.com> (raw)
In-Reply-To: <CADEOadfBZeJD=tBJq0gyfdDa=GA6iS3zP23jt1k44hSzKrxrPQ@mail.gmail.com>
On Thu, May 23, 2024 at 4:25 PM Damien Mattei <damien.mattei@gmail.com> wrote:
> On Thu, May 23, 2024 at 12:37 AM Jeronimo Pellegrini <j_p@aleph0.info> wrote:
>> On 2024-05-22 18:07, Pierpaolo Bernardi wrote:
>> > In chez:
>> >
>> >> (cond (else (define x 7) x))
>> > 7
>> >> x
>> > 7
>> >
>> > which looks like a bug to me.
> yes i spent many hours debugging to understand why
> (cond (else (define y 7) y)) worked and not (cond (#t (define x 7) x))
I had and explanation from Jamie Taylor.
The implementations which behave like Chez, are probably using the
example definition of the cond syntax given in appendix B of the R6
report, which expands (cond (else result1 result2 ...)) into (begin
result1 result2 ...). Given the splicing nature of begin, when the
cond is in a context valid for definitions we have the weird result
above.
https://github.com/cisco/ChezScheme/issues/835
next prev parent reply other threads:[~2024-05-23 14:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 19:26 cond clause does not allow definitions Damien Mattei
2024-05-22 20:07 ` Jeronimo Pellegrini
2024-05-22 20:33 ` Damien Mattei
2024-05-22 20:34 ` Damien Mattei
2024-05-22 20:37 ` lloda
2024-05-22 20:40 ` lloda
2024-05-22 21:07 ` Pierpaolo Bernardi
2024-05-22 22:09 ` Damien Mattei
2024-05-22 22:37 ` Jeronimo Pellegrini
2024-05-23 14:25 ` Damien Mattei
2024-05-23 14:59 ` Pierpaolo Bernardi [this message]
2024-05-22 22:12 ` Maxime Devos
2024-05-22 22:34 ` Damien Mattei
2024-05-24 14:27 ` Linus Björnstam
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='CANY8u7E=0DE-+a44LnLzsAYf1arTAfdrj_YwGGuUXVaC7tsoog@mail.gmail.com' \
--to=olopierpa@gmail.com \
--cc=damien.mattei@gmail.com \
--cc=guile-user@gnu.org \
--cc=j_p@aleph0.info \
/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).