[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: parser variables persist beyond { } scope
|
From: |
Han-Wen Nienhuys |
|
Subject: |
Re: parser variables persist beyond { } scope |
|
Date: |
Thu, 6 Aug 2009 11:43:18 -0300 |
On Thu, Aug 6, 2009 at 11:19 AM, Mark Polesky<address@hidden> wrote:
>
> Han-Wen Nienhuys wrote:
>
>> I think in general the manual should not encourage users to define or
>> set variables using Scheme, exactly because the scoping semantics are
>> confusing.
>
> I just had an idea. Why not make afterGraceFraction a context property
> for Score? Wouldn't that solve all of these problems?
>
> I'm actually not sure -- let me know.
No, afterGrace does not work like that. It's music function, so it
runs before contexts are created.
--
Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen
- Re: parser variables persist beyond { } scope, Ian Hulin, 2009/08/04
- Re: parser variables persist beyond { } scope, Han-Wen Nienhuys, 2009/08/04
- Re: parser variables persist beyond { } scope, Mark Polesky, 2009/08/06
- Re: parser variables persist beyond { } scope, Mark Polesky, 2009/08/06
- Re: parser variables persist beyond { } scope, John Mandereau, 2009/08/06
- Re: parser variables persist beyond { } scope, Reinhold Kainhofer, 2009/08/06
- Re: parser variables persist beyond { } scope, Werner LEMBERG, 2009/08/07
- Re: parser variables persist beyond { } scope, Mark Polesky, 2009/08/07
- Re: parser variables persist beyond { } scope, Reinhold Kainhofer, 2009/08/07
- Re: parser variables persist beyond { } scope, John Mandereau, 2009/08/09