On 4/6/06, David Feuer <[EMAIL PROTECTED]> wrote: > 2. The more I read the code and think about it, the more I think > stencil interpretation should be pushed to the back end and written in > Scheme.
Put this another way: instead of having the common stencil code drive the backends, the backends should use the common code if and when they find it useful. Common code could include font listing functions, tree folds, and other traversal combinators. Rather than arbitrary Scheme expressions, stencil leaves would describe their contents. This will often look pretty similar, but it gives tremendously more flexibility to the backend, particularly in how it chooses to implement coordinate transformations, but also in how it deals with fonts. David Feuer _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
