Kim Shrier <[email protected]> writes: > On Apr 14, 2018, at 2:48 AM, David Kastrup <[email protected]> wrote: >> >> Kim Shrier <[email protected]> writes: >> >>> Just to satisfy personal curiosity, I am looking at the lilypond source code >>> so I can get a better feel for what it is up to and how it accomplishes its >>> job. >>> >>> My understanding is that the parser constructs a scheme data structure >>> which is subsequently processed by the iterators to turn it into a stream >>> (or several streams) of musical events. Before I start looking at the >>> iterators, I would like to see what they are working with for input. >>> >>> So, I have a few questions. >>> >>> Is my understanding correct that the parser produces a single scheme >>> expression that is then processed for use in later stages? >> >> No. The parser calls various hook functions for processing elements >> encountered in the input such as scores, markups, books, bookparts. > > I got that mistaken impression from reading Erik Sandberg’s paper.
Erik Sandberg's paper is not LilyPond documentation. It documents an experimental branch for the code he used in his thesis long long ago that was to significant degrees not folded into LilyPond proper. -- David Kastrup _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
