On 2013/03/23 16:38:21, t.daniels_treda.co.uk wrote:
A 'programming error' should be issued only when an internal
inconsistency
in LilyPond's code or data structures is detected. Any such message
should
always result in a bug being reported and tracked. If the problem is
due to
suspect user code a warning or error should be issued. In this case
maybe
a warning is appropriate.
Thanks, Trevor! This sheds some light on this situation. After rereading David's comments i've come to the conclusion that there should be no programming errors reported when extents are empty, so i've sent a new patchset which makes Lily behaviour consistent in this regard. thanks, Janek https://codereview.appspot.com/7533046/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
