Simon Albrecht <[email protected]> writes:

> On 17.02.2016 13:27, David Kastrup wrote:
>> Graham King<[email protected]>  writes:
>>
>>>
>>>            \book {
>>>              music = \relative { c' d e f }
>>>              \score {
>>>               \music
>>>              }
>>>            }
>> The problem is that it would likely be possible to teach LilyPond's
>> parser to accept the latter, but due to book not having a scope of its
>> own for music expressions, it would be perfectly equivalent to the
>> first: any such assignment would change "music" globally.
>
> A possibility to define variables (in proper LilyPond syntax) inside
> of \book or \bookpart environments would be really great to have, in
> order to simplify working with large projects, many includes and
> different target editions. I don’t think that not having a proper
> scope for each book/bookpart is a problem.

I think it is.

> So I’d vote for this change.

I vote against it.  It does not make sense that when I write

mybook =
\book {
   zap = 3
   ...
}

that at the time mybook is actually being interpreted, zap might have a
completely different value.

If you want to make global assignments, make global assignments.

-- 
David Kastrup

_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to