>> If someone is going to rewrite the algorithm, the order of events
>> should be obeyed.
>
> For simultaneous events, LilyPond has no order.
Oh. This means that
c'\startGroup\stopGroup
and
c'\stopGroup\startGroup
can't be reliably distinguished?
> That's why one needs to have one phase for recording events and
> another for doing something based on them.
Hmm. I got the impression that `listen_note_grouping' is this
recording-events phase.
> Maybe the infamous issue 34 could be tackled as part of that
> mechanism? Not sure about that.
It would be nice if we find a solution for that.
Werner
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
