[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Change of behavior for `define*'?
From: |
Patrick McCarty |
Subject: |
Change of behavior for `define*'? |
Date: |
Sun, 10 Jan 2010 18:48:44 -0800 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
Hi,
I'm trying to get LilyPond compiling with Guile git (commit 7cd554),
and I'm running into a problem that I don't see documented in NEWS.
With Guile 1.8.7, this code is valid:
guile> (use-modules (ice-9 optargs))
guile> (define* a 1)
guile> a
1
But with git, I get the following:
scheme@(guile-user)> (define* a 1)
Throw to key `syntax-error':
ERROR: In procedure sc-expand:
ERROR: source expression failed to match any pattern in (define* a 1)
Is this an intentional change of behavior in Guile, or is it a bug?
Thanks in advance,
-Patrick
- Change of behavior for `define*'?,
Patrick McCarty <=