Re: [Lilypond-auto] Issue 4093 in lilypond: put NullVoice in Staff by default

[lilypond]

Comment #5 on issue 4093 by address@hidden: put NullVoice in Staff by default
https://code.google.com/p/lilypond/issues/detail?id=4093

And I protested against that patch even then.

To accommodate this properly might necessitate changes in C++.  As a rule  
of thumb, take the first naive approach of trying to get the desired  
functionality and then "make it so that it works" by changing fundamentally  
what kept it from working.  We don't want to implement things by poking  
around in internals.  If the internals don't fit, we either need to change  
them outright, or provide clean knobs for adapting their behavior.   
Providing knobs is the worse alternative of the two since it means the user  
has to chose between useful functionalities rather than have all.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings