lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Updated stream/parser todo


From: Erik Sandberg
Subject: Re: Updated stream/parser todo
Date: Tue, 27 Jun 2006 08:14:17 +0200
User-agent: KMail/1.9.1

On Monday 19 June 2006 16:02, Erik Sandberg wrote:
> On 6/19/06, Han-Wen Nienhuys <address@hidden> wrote:
> > Erik Sandberg schreef
> > > BTW: May I change Sequential_iterator::get_music_list to return
> > > something like scm_call_1 (get_music ()->get_property
> > > ("child-list-callback"), get_music ()->self_scm ());
> > > ?
> > >
> > > This would make it possible to soft-code e.g. percent-repeat-iterator.
> >
> >
> > but, all in all, I don't see what advantage this would get us.
> 
> Custom iterators makes it easier to make music expressions more
> abstract, in the sense that the current time-scaled-music is abstract
> (one music expression can acts as an alias for a more complex pattern
> of nested expressions). Writing a two-line Scheme function is IMHO
> easier and more elegant than creating a new iterator C++ module.
>
> In most examples I've seen so far, customised Sequential-iterators
> seem to be sufficient for abstracting music expressions.

The attached patch makes my proposed change to sequential-iterators, and uses 
this to clean up multi measure rests. The patch obsoletes the following:
- glue-mm-rests
- MultiMeasureRestMusicGroup
- Sequential_music_iterator

I know mm rests can be further cleaned up by creating spanner events, but I 
won't do that this time (IIRC you want to do some related cleanups of mm 
rests, and I want to avoid double work)

-- 
Erik

Attachment: es-060627.diff
Description: Text Data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]