Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default.

[lilypond]

Comment #22 on issue 2070 by address@hidden: Patch: Don't wrap EventChord  
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070

@mike: of course I'll get the terminology wrong: my amount of knowledge is  
just sufficient for buzzword juggling.  Second option sounds better.  I  
would prefer if I did not need to meddle with the music by tagging  
on "contained-in-event-chord" (which, if we want to be pedantic, would be  
the right kind of operation).  Is there another way in which the EventChord  
can report an ArticulationEvent and have the NoteEvent iterator (?) know  
that it does not need to cater for the ArticulationEvent any more?  Perhaps  
it should just iterate itself through its contained events and call a  
different iterator, or the same iterator with some "hidden argument"?  It  
would be possible to create a copy of the NoteEvent with all articulations  
already treated by the EventChord iterator removed, but I would prefer  
avoiding this kind of additional copying.  Just handing the NoteEvent  
engraver an additional list of ArticulationEvents it should just ignore  
sounds like a nicer option.  It would likely not be a noticeable  
performance problem if this list was created per-EventChord rather than  
per-NoteEvent.