Can we please raise this as a bug in the bug tracker? I encounter this situation frequently in my scores.
Andrew On 26 May 2016 at 21:16, David Kastrup <[email protected]> wrote: > Andrew Bernard <[email protected]> writes: > >> Thanks. Do we raise a bug? The program stops and will not continue to >> compile after this error. > > Like after any failed assertion since an assertion indicates that the > program cannot continue sensibly. > > So yes, that's a bug. The proper fix is finding out under which > conditions the assertion failure can trigger and then figure out how to > proceed in this case or how to avoid it. > > The bandaid fix would be replacing the assertion failure with a > programming error as long as one can state with confidence that it will > not result in a hard crash. _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
