Re: Merge Rests Engraver

[Carl Sorensen]

On 2/21/12 10:38 PM, "Jay Anderson" <address@hidden> wrote:

>I want to open up the conversation about merging rests again (see bug
>1228 http://code.google.com/p/lilypond/issues/detail?id=1228). Below
>is a first go at a scheme based engraver. It doesn't kill any grobs so
>the chance of segfaults is lower. Do overlapping grobs have any other
>unintended consequences? I haven't spent much time testing it yet
>besides the attached examples and a couple other scores. It seems to
>work well enough. Let me know if you see any ways it can be
>simplified.

If this were a C++ engraver, I would expect the unused grobs to be
suicided.  Is there a reason not to do this in a scheme engraver?  I think
it is unwise to keep multiple copies of a grob around and trust that they
are the same.

Thanks,

Carl