Re: grob creation

[Rune Zedeler]

Citat Han-Wen Nienhuys <address@hidden>:

> because the result of an acknowledged grob may be a new grob. That new
> grob must be acked, and the result may be another grob. The cycle is
> continued until no new grobs are created.  (example: Note head leads
> to stem. Stem leads to beam.)

Thanks. Perhaps more questions later.

> The accidental engraver is hard in the
> sense that it must know about the absence of some grob types (eg.
> tie), and there is no mechanism that will tell "there will be no Ties
> created in this time-step.".
> If you postpone announcing the grob, no engraver will notice it in the
> same time step, and it will be noticed in the next (incorrect) time
> step.  ATM, no engravers acknowledge accidental-interface, your
> approach will work.

Okay, I keep on working then.

> It would be technically more correct to make an accidental if there is
> reason, and kill it off later when it is not needed, but that might
> lead to excessive grob creation.

Well, yes wouldn't that lead to spacing problems and problems with 
accidental_placement?

> In any event, the special behavior
> of the acc-engraver should be thoroughly documented, as it will always
> be special.

Yes. First I'll make it work, then I'll docu it (currently the code should be 
finished, but all the accidentals have gone :-( )

-Rune