On 28 April 2010 13:41, David Kastrup <d...@gnu.org> wrote: > And if each engraver specifies what engravers it is relying on in a > machine-readable manner (or the respective order in which it wants to be > applied), then Lilypond can actually do the required sorting and figure > out a proper order at runtime.
I agree, there's no point in providing automated documentation unless the dependencies are also resolved automatically (which turns it from being a quick frog task into something a bit more involved). There's already limited support for ordering via the method Translator::must_be_last () (and must-be-last in a scheme engraver), which is used to ensure Axis_group_engraver is always the last engraver in a context definition. Cheers, Neil _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
