Graham Percival <gra...@percival-music.ca> writes: > On Wed, Jun 9, 2010 at 4:55 PM, James Bailey > <derhindem...@googlemail.com> wrote: >> Am I to understand that a programming error should have a bug report? > > Yes; current policy is to record all warnings (even "false warnings", > which produce good output but include an unexpected error/warning > message on the console). This is a change from a few years ago, and > will probably add 100-200 extra issues, but there was strong feelings > towards adding them.
"programming error" basically means that something happened that should never happen. If there had been no programming involved on part of the user, it is a problem in the existing Lilypond code. "programming error" also implies that the action taken (if it is not a straight abort) is just a best shot at dealing with a case that has been deemed impossible. It is probably a bit too optimistic to assume that such a best shot will always lead to correct results. -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
