From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Fwd: Guile interpeter crash
Date: Tue, 1 Oct 2013 18:42:57 +0200 [thread overview]
Message-ID: <CAMFYt2bKn=xNEMWODZ_gJ=3F5RBftK3MVxe7bHknHgpK5+G4Xw@mail.gmail.com> (raw)
In-Reply-To: <CAMFYt2avxvU_Vd-oBObtNq43qaU9wCLq=K=AHaLWJMmvrzq=pA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
---------- Forwarded message ----------
From: Panicz Maciej Godek <godek.maciek@gmail.com>
Date: 2013/10/1
Subject: Re: Guile interpeter crash
To: Dmitry Bogatov <KAction@gnu.org>
2013/10/1 Dmitry Bogatov <KAction@gnu.org>
>
> Here is code that results crash (return 134). Hope it is interesting.
>
The code you gave is not a proper Scheme program.
C.f.
http://www.schemers.org/Documents/Standards/R5RS/HTML/r5rs-Z-H-8.html#%_sec_5.3,
excerpt:
Although macros may expand into definitions and syntax definitions in any
context that permits them, it is an error for a definition or syntax
definition to shadow a syntactic keyword whose meaning is needed to
determine whether some form in the group of forms that contains the
shadowing definition is in fact a definition, or, for internal definitions,
is needed to determine the boundary between the group and the expressions
that follow the group
In other words, you cannot redefine define. I suppose the interpreter falls
into infinite loop when it tries to substitute define# with define, and
then define -- with define#.
That being said, I don't think it's fortunate to use the # character within
a symbol.
Best regards,
M.
[-- Attachment #2: Type: text/html, Size: 2165 bytes --]
next prev parent reply other threads:[~2013-10-01 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 15:15 Guile interpeter crash Dmitry Bogatov
[not found] ` <CAMFYt2avxvU_Vd-oBObtNq43qaU9wCLq=K=AHaLWJMmvrzq=pA@mail.gmail.com>
2013-10-01 16:42 ` Panicz Maciej Godek [this message]
2013-10-01 20:34 ` Fwd: " Mark H Weaver
2013-10-02 7:13 ` Dmitry Bogatov
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='CAMFYt2bKn=xNEMWODZ_gJ=3F5RBftK3MVxe7bHknHgpK5+G4Xw@mail.gmail.com' \
--to=godek.maciek@gmail.com \
--cc=guile-devel@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).