On Thu, Jan 28, 2010 at 11:49 AM, David Kastrup <d...@gnu.org> wrote: > Carl Sorensen <c_soren...@byu.edu> writes: > >> On 1/28/10 7:25 AM, "David Kastrup" <d...@gnu.org> wrote: >> >>> Anyway, I think that likely the ambitus engraver would be a good >>> candidate for reimplementing as a Scheme engraver. It would appear >>> reasonably straightforward but not trivially so, and it is one of those >>> things where augmenting the _code_ and behavior is likely to be better >>> extensible in Scheme. >> >> I think it would be difficult to implement as a Scheme engraver, >> because there need to be variables stored as part of the context that >> are modified by different event handlers. But I could be wrong. It >> wouldn't be the first time and is not likely to be the last.
do you mean engravers by 'event handlers' ? I had thought the Scheme engravers to use context properties to store internal state, but if that is a problem, we could add another internal scope inside the C++ engraver instance to store private data. Public data can of course be shared as context property. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
