Comment #6 on issue 1894 by d...@gnu.org: Prunes stem::length down to the
bare minimum
http://code.google.com/p/lilypond/issues/detail?id=1894
I've just read the commit message:
This reduces the chance that there will be a programming error when
looking
for a Bezier intersection, as grobs that no longer intersect with the
slur
will not be considered for shifting.
Mike, that sounds very wrong. A "programming error" is basically a failed
assertion: something happens which, according to the logic of the program,
can't possibly happen. "reducing the chance that there will be a
programming error" is nonsense. Either we know that this message can still
trigger and for what reason, and then we need to design a useful behavior
for that case since it is not a "programming error", or we know that it
can't trigger, then we should not bother about the likelihood, or we know
that this message can still trigger but not why, then it is a bad idea
masking the problem by reducing its visibility.
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
