Re: Lilypond error behaviour

[Urs Liska]

Am 17. April 2016 08:20:52 MESZ, schrieb David Kastrup <address@hidden>:
>Andrew Bernard <address@hidden> writes:
>
>> If you look at the MWE example I provided to illustrate what I
>believe
>> is misleading information about a ‘FATAL’ error, then it has plain
>> text which it ignores, claims a fatal error and proceeds to make a
>> perfectly good PDF.
>
>LilyPond wouldn't know that, and in any way it returns an ERROR message
>and an ERROR code.
>
>I don't know why you are obsessed about LilyPond not touching the PDF
>(in which case you still would not have an idea about whether LilyPond
>was successful unless you checked the PDF's modification date) or
>trying
>to leave behind an invalid PDF file (in which case you need to call a
>PDF verification program in order to figure out whether there was an
>error).
>
>Also, some runs of LilyPond may produce a PDF with a different name or
>indeed no PDF at all (you can run LilyPond for indexing purposes or
>information gathering and a number of other things).
>
>> Based on this it means one can have blocks of text as comments or
>> documentation with no syntax, happily ignore the error, and have a
>> nice new way of annotating lilypoind source code files. I hope people
>> can see that this is clearly absurd.
>
>It is not LilyPond's task to make it harder for people to ignore errors
>when they really try hard.
>
>> It’s the FATAL error message that I am questioning. That terminology
>> in my IT world means the program cannot go on. It’s a simply
>> confusing. adjective. One could say given the behaviour that it
>should
>> be a warning.
>
>A warning is appropriate for something which is not an error: namely
>LilyPond has a well-specified task but the results will not likely make
>sense.  LilyPond does not return an error code for a warning.

Well, then let LilyPond report an error when it encounters one. But only then a 
"fatal" one when it actually forces LilyPond to stop.

It is in no way a fatal error to have \version "2.19.39" in a file and compile 
it with 2.19.38. It just exposes a *certain* risk of problems.

>
>-- 
>David Kastrup
>
>_______________________________________________
>lilypond-user mailing list
>address@hidden
>https://lists.gnu.org/mailman/listinfo/lilypond-user

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.