I have not used any language of complaint, merely observation and puzzlement. It was also not I that mentioned it is a regular source of confusion. Others do seem to think so. As to being the first, I may possibly be the first to write a lilypond compile server where I need to understand clearly the error conditions to get everything working nicely.
So gentlemen, since this is a regular source of confusion,
You are the first to have complained.
As to lilypond making a best effort at producing output, I have never seen this referred to in the NR. That ought to go in somewhere. But for my preference, a serious syntax error which is just outright garbage should in my opinion not produce any output. Other types of compilers would stop.
As does LilyPond.
But it does not stop. After the syntax error it still produces the output PDF, and states a 'fatal error' happened. Perhaps it could say that 'a syntax occurred but I overall I was able to carry on regardless in this case’ or something to that effect. I thought the common understanding of fatal error means that the program cannot continue processing because of it. I am only talking about the processing of one file here, as per the submitted MWE, not the processing of more than one file on the command line.
Andrew
|