Reviewers: MikeSol,
Message:
On 2012/01/17 17:42:38, MikeSol wrote:
I would advise not handling it this way - the function to_event is
supposed to
take music and return an event. In this patch, it is taking music,
returning an
event, and maybe broadcasting music and/or sending it to a conte
I still think this patch goes outside the model of the way these things
are usually designed in LilyPond. I'm not saying that LilyPond's design
paradigm is objectively good or bad (I truly have no idea, as I know
nothing about any other piece of software), but I think it's best to
follow it whene
I would advise not handling it this way - the function to_event is
supposed to take music and return an event. In this patch, it is taking
music, returning an event, and maybe broadcasting music and/or sending
it to a context.
I'd recommend creating a new iterator, rhythmic-music-iterator, that