Re:Lilypond error behaviour

[Peter Gentry]

The errors that I frequently make show up as an additional empty stave or a ridiculously over long bar that runs off the page. This alerts me to an error but I have to search for it and they can be be very simple typos. Error messages in the log may also be a later result of the error rather than pin pointing its location so some digging is usually required.

 

This seems fine to me as all you have to do is work through the input step by step to loacte the error. It would be difficult (impossible) to pick out all input errors in programs like Lilypond compared to familar number crunching codes, how the heck does the code know what your intentions are and what is an "error" in your source.

 

Lets not ask the impossible of hard pressed developers.

 

regards
Peter Gentry