public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
* Re: "define-constant is only allowed in a <body>"
       [not found] <CAMFYt2awE_4SU9GYhKaoaG3JCiotKMech+B_j10SqD=an1sTbQ@mail.gmail.com>
@ 2022-11-20 22:41 ` Per Bothner
  0 siblings, 0 replies; only message in thread
From: Per Bothner @ 2022-11-20 22:41 UTC (permalink / raw)
  To: Panicz Maciej Godek, kawa



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/

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2022-11-20 22:41 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <CAMFYt2awE_4SU9GYhKaoaG3JCiotKMech+B_j10SqD=an1sTbQ@mail.gmail.com>
2022-11-20 22:41 ` "define-constant is only allowed in a <body>" Per Bothner

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).