[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: parser variables persist beyond { } scope
From: |
Mark Polesky |
Subject: |
Re: parser variables persist beyond { } scope |
Date: |
Fri, 31 Jul 2009 12:51:06 -0700 (PDT) |
Trevor Daniels wrote:
> No, I don't think this is a *common* error.
> I've never seen it mentioned on -user. And
> it's too obscure for the LM anyway.
>
> What we could do is add a full explanation of
> parser (or global) variables in NR 6.8 "Difficult
> tweaks", together with your warning, and reference
> that from each of the examples in the docs that
> uses them. This accords with the established
> style of the NR. Your handy lists, below, could
> also be included.
>
> If you're happy with this, and there are no adverse
> comments over the next couple of days, I'll initiate
> it. I will need some help from you to hone the text
> though.
I'm okay with it. But I'd like to see what the others think. Am
I correct in thinking that if an object returns #t for this test
from within a .ly file, it qualifies as a "parser variable"?
#(defined? 'object-name)
- Mark
- parser variables persist beyond { } scope, Mark Polesky, 2009/07/30
- Re: parser variables persist beyond { } scope, Werner LEMBERG, 2009/07/30
- Re: parser variables persist beyond { } scope, Han-Wen Nienhuys, 2009/07/31
- Re: parser variables persist beyond { } scope, Mark Polesky, 2009/07/31
- Re: parser variables persist beyond { } scope, Han-Wen Nienhuys, 2009/07/31
- Re: parser variables persist beyond { } scope, Mark Polesky, 2009/07/31
- Re: parser variables persist beyond { } scope, Trevor Daniels, 2009/07/31
- Re: parser variables persist beyond { } scope,
Mark Polesky <=
- Re: parser variables persist beyond { } scope, Trevor Daniels, 2009/07/31
- Re: parser variables persist beyond { } scope, Patrick McCarty, 2009/07/31
- Re: parser variables persist beyond { } scope, Neil Puttock, 2009/07/31