From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: kawa@sourceware.org
Subject: Re: "define-constant is only allowed in a <body>"
Date: Mon, 21 Nov 2022 00:29:05 +0100 [thread overview]
Message-ID: <CAMFYt2YcG80-Hmvm7fQmCQYWiGPjNnbODxHguznvkux9V0hGQA@mail.gmail.com> (raw)
In-Reply-To: <6d811ecb-2c95-a973-9e78-279f5e608883@bothner.com>
[-- Attachment #1: Type: text/plain, Size: 2182 bytes --]
niedz., 20 lis 2022 o 23:41 Per Bothner <per@bothner.com> napisał(a):
>
>
> 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 ...))
>
>
I understand this message the way you explained it
-- it just doesn't make sense in my context.
There seems to be an issue with module dependency resolution.
The problematic expansion was in the (panel) module.
It contains a dependency on the (mapping) module.
The main module (either grasp-terminal.scm or grasp-desktop.scm)
included (import (panel)), and the compilation failed with the above
message.
But when I add (import (mapping)) to the main module -- before the
(import (panel)) clause -- the compilation succeeds. (However, if I add it
after (import (panel)) -- it still breaks).
I realized that I ran into that problem early on during my work,
but instead of reporting it, I just started including module dependencies
transitively in the "right order". This is a workaround, but I think
that there might be some issue between reflection, macro expansion
and module dependency loading.
I'll let you know if I manage to find a minimal set of modules which break
in this way.
prev parent reply other threads:[~2022-11-20 23:29 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
2022-11-20 23:29 ` Panicz Maciej Godek [this message]
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=CAMFYt2YcG80-Hmvm7fQmCQYWiGPjNnbODxHguznvkux9V0hGQA@mail.gmail.com \
--to=godek.maciek@gmail.com \
--cc=kawa@sourceware.org \
--cc=per@bothner.com \
/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).