From: Per Bothner <per@bothner.com>
To: Panicz Maciej Godek <godek.maciek@gmail.com>, kawa@sourceware.org
Subject: Re: "define-constant is only allowed in a <body>"
Date: Sun, 20 Nov 2022 14:41:28 -0800 [thread overview]
Message-ID: <6d811ecb-2c95-a973-9e78-279f5e608883@bothner.com> (raw)
In-Reply-To: <CAMFYt2awE_4SU9GYhKaoaG3JCiotKMech+B_j10SqD=an1sTbQ@mail.gmail.com>
On 11/19/22 06:37, Panicz Maciej Godek via Kawa wrote:
> When I try to use this code from yet another module -- more specifically,
> this one:
>
> https://github.com/panicz/grasp-android/blob/master/stages/retreat/GRASP/src/panel.scm#L130
>
> as
>
> (define-mapping (on-key-press code) never)
>
> I get the error message
>
> define-constant is only allowed in a <body>
>
> but when I use the expanded version
>
> (define on-key-press (mapping (code) never))
>
> everything works.
>
> I wonder what could be the reason of Kawa's behavior.
Kawa is presumably complaining that the define-early-constant is
in a non-<body> context.
This is allowed:
(begin (define-early-constant ...) ...)
This is not:
(list (define-early-constant ...) ...)
One of the problems with Scheme S-expression-based syntax is that
it is sometimes tricky to tell what parenthesis does what.
For example, it is easy to end up with this after some macro-expansion:
((define-early-constant ...))
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2022-11-20 22:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 14:37 Panicz Maciej Godek
2022-11-20 22:41 ` Per Bothner [this message]
2022-11-20 23:29 ` Panicz Maciej Godek
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=6d811ecb-2c95-a973-9e78-279f5e608883@bothner.com \
--to=per@bothner.com \
--cc=godek.maciek@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).