Comment #2 on issue 1987 by d...@gnu.org: Patch: Get rid of most of the insane string-tunings API
http://code.google.com/p/lilypond/issues/detail?id=1987
It uses much fewer #{ ... #} commands during initialization. And it just stores pitch lists instead of whole chords. Maybe storing the whole chord (which is a music expression) keeps its generating parser clone alive via its 'origin field?
Maybe we should try to avoid cloning the parser for every #{ ... #}. The [string] messages in verbose mode are annoying anyway.
I still don't quite get the process regarding convert-ly rules. Do I check in the results of the convert-ly run as a separate commit? For one thing, that would make one commit deliver a non-working master. Do I check in both unconverted and converted as a single commit of a 2-commit branch?
But the conversion should only be done when bumping the version number at the same time, right?
Actually, convert-ly also touches stuff from Mike from a much earlier version. Great.
_______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
