Re: Partial compilation (again)

[David Kastrup]

Urs Liska <address@hidden> writes:

> Am 21. November 2014 12:36:59 MEZ, schrieb David Kastrup <address@hidden>:
>
>>So I don't see this going anywhere fast.  To get a hook into cloning
>>internal engraver states, you'd probably want to create a more
>>object-oriented frame work for them.
>
> Ok, I see. Thank you for the explanation. 
>
> I'll try if I can get *somewhere* with an "external" approach as
> outlined on -user.

TeX, in contrast to LilyPond, works in a pipeline-like manner, producing
output all the time.  In that case, a semi-external approach might work
when you have a good idea what kind of input is subject to editing: you
just fork off a copy of the executable when it gets to the place before
the editing region.  And then you run that forked copy on the changed
input from that point on.

However, LilyPond first consumes all input and then starts processing,
so the input file pointer into an unchanged part of the input is just
not a useful indicator of LilyPond's progress and this kind of low-level
approach does not look workable.

-- 
David Kastrup