[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
New read/eval Scheme syntax inconsistent in handling existing code
From: |
Valentin Villenave |
Subject: |
New read/eval Scheme syntax inconsistent in handling existing code |
Date: |
Mon, 21 Nov 2011 19:00:16 +0100 |
Greetings everybody,
David's new code with #/$(scheme) styles does offer a lot of exciting
possibilities... but it is also hugely disruptive when it comes to
existing code! Consider for instance the following:
\version "2.15.19"
myvar = { b'4 }
#(ly:parser-include-string parser
"myvar = { a'2 }")
\new Staff \myvar
This used to print the overwritten variable, which it doesn't anymore
and I think I get why.
What's a lot more baffling, however, is that the variable isn't
overwritten _even_ when prefixing the Scheme expression with $ instead
of #.
(At least it isn't overwritten until after Lily's already parsed and
processed the staff.)
Thoughts?
Valentin.
- New read/eval Scheme syntax inconsistent in handling existing code,
Valentin Villenave <=
Re: New read/eval Scheme syntax inconsistent in handling existing code, David Kastrup, 2011/11/21