From: Han-Wen Nienhuys <hanwenn@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guile-devel@gnu.org
Subject: Re: unhandled constant?
Date: Thu, 30 Jan 2020 09:05:17 +0100 [thread overview]
Message-ID: <CAOw_e7bajESrGP-5EKZPqf-Diztj3kkC1oxJTLPBn+CGgW2Lsg@mail.gmail.com> (raw)
In-Reply-To: <87r1ziti8g.fsf@elephly.net>
[guile1.8]$ grep -ir define-syntax-rule .
(empty)
I need something that works in GUILE 1.8 too.
this is what I got from David Kastrup:
>Got any comments about macros being sooo yesterday compared to syntax
forms? Syntax forms actually don't work in LilyPond: there was an
incompatibility because the 1.8 implementation will balk if some symbol
used in syntax forms already has a definition, and we have that. I
forgot the exact symbol at fault. I think it was some music function
name.
Would there be a way that we can use our source code unchanged with GUILE 2.2?
Can you explain why I get this error message?
On Wed, Jan 29, 2020 at 4:06 PM Ricardo Wurmus <rekado@elephly.net> wrote:
>
>
> Han-Wen Nienhuys <hanwenn@gmail.com> writes:
>
> > Some of the lilypond Scheme files do the following:
> >
> >
> > (define decl '())
> > (define (make-var n v) (list "var" n v))
> > (defmacro define-session (name value)
> > (define (inner n v)
> > (set! decl
> > (cons
> > (make-var n v)
> > decl))
> > )
> > `(,inner ',name ,value))
> > (define-session foo 1)
> > (display decl)
> > (newline)
> >
> > In GUILE 2.2, this yields
> >
> > ;;; WARNING: compilation of /home/hanwen/vc/lilypond/q.scm failed:
> > ;;; unhandled constant #<procedure inner (a b)>
> >
> > What does this error message mean, and what should I do to address the problem?
>
> Would it be feasible to use define-syntax-rule here?
>
> --8<---------------cut here---------------start------------->8---
> (define decl '())
> (define (make-var n v) (list "var" n v))
> (define-syntax-rule (define-session name value)
> (let ((inner (lambda (n v)
> (set! decl
> (cons
> (make-var n v)
> decl)))))
> (inner 'name value)))
> (define-session foo 1)
> (display decl)
> (newline)
> --8<---------------cut here---------------end--------------->8---
>
>
> --
> Ricardo
--
Han-Wen Nienhuys - hanwenn@gmail.com - http://www.xs4all.nl/~hanwen
next prev parent reply other threads:[~2020-01-30 8:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 23:08 unhandled constant? Han-Wen Nienhuys
2020-01-29 15:06 ` Ricardo Wurmus
2020-01-30 8:05 ` Han-Wen Nienhuys [this message]
2020-01-31 10:49 ` Han-Wen Nienhuys
2020-01-31 11:17 ` Ricardo Wurmus
2020-02-02 19:30 ` Jan Nieuwenhuizen
2020-01-31 14:57 ` Linus Björnstam
2020-01-31 15:16 ` Han-Wen Nienhuys
2020-01-31 17:50 ` Han-Wen Nienhuys
2020-01-31 18:19 ` Linus Björnstam
2020-01-31 19:17 ` Han-Wen Nienhuys
2020-01-31 19:52 ` Linus Björnstam
2020-01-31 20:01 ` Linus Björnstam
2020-02-01 9:54 ` Han-Wen Nienhuys
2020-02-01 9:56 ` Han-Wen Nienhuys
2020-02-01 10:10 ` David Kastrup
2020-02-01 11:23 ` Han-Wen Nienhuys
2020-02-01 11:36 ` David Kastrup
2020-02-01 13:12 ` Linus Björnstam
2020-02-01 11:09 ` David Kastrup
2020-02-01 13:16 ` Linus Björnstam
2020-02-01 14:23 ` David Kastrup
2020-02-01 15:21 ` Linus Björnstam
2020-02-01 21:55 ` Taylan Kammer
2020-02-01 21:58 ` Fwd: " Taylan Kammer
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=CAOw_e7bajESrGP-5EKZPqf-Diztj3kkC1oxJTLPBn+CGgW2Lsg@mail.gmail.com \
--to=hanwenn@gmail.com \
--cc=guile-devel@gnu.org \
--cc=rekado@elephly.net \
/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).