[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Lilypond error behaviour
From: |
Sharon Rosner |
Subject: |
Re: Lilypond error behaviour |
Date: |
Tue, 19 Apr 2016 00:12:25 +0200 |
> And secondly, to me it seems clear why the error is termed "fatal" - the
> parser aborted. You don't want a compilation error to return a fatal error to
> "make" and, because it receives a fatal error, make throws a fatal error and
> crashes too, do you? The question is WHERE in the stack do we actually trap
> and handle the error.
No. As I demonstrated, the parser in fact does not abort. It continues
correctly parsing the rest of the input after encountering the error. So what
is exactly “fatal” here?
> Lilypond, imho, makes the correct decision FOR THE USER, traps the error, and
> then turns the incomplete output, from the *crashed* parser, into an
> incomplete pdf.
Again, these are two separate things. The fact that Lilypond continues
processing the input is fine. The error reporting to me seems misleading.
Sharon
- Re: Lilypond error behaviour, (continued)
- Re: Lilypond error behaviour, Sharon Rosner, 2016/04/17
- Re: Lilypond error behaviour, David Kastrup, 2016/04/17
- Re: Lilypond error behaviour, Sharon Rosner, 2016/04/18
- Re: Lilypond error behaviour, mskala, 2016/04/18
- Re: Lilypond error behaviour, David Wright, 2016/04/18
- Re: Lilypond error behaviour, mskala, 2016/04/18
- Re: Lilypond error behaviour, David Kastrup, 2016/04/18
- Re: Lilypond error behaviour, mskala, 2016/04/18
- Re: Lilypond error behaviour, Sharon Rosner, 2016/04/18
- Re: Lilypond error behaviour, Anthonys Lists, 2016/04/18
- Re: Lilypond error behaviour,
Sharon Rosner <=
- Re: Lilypond error behaviour, Sharon Rosner, 2016/04/18
- Re: Lilypond error behaviour, Noeck, 2016/04/19
- Re: Lilypond error behaviour, mskala, 2016/04/19
- Re: Lilypond error behaviour, Thomas Morley, 2016/04/19
- Re: Lilypond error behaviour, mskala, 2016/04/19
- Re: Lilypond error behaviour, David Kastrup, 2016/04/19
- Re: Lilypond error behaviour, Sharon Rosner, 2016/04/19
Re: Lilypond error behaviour, Andrew Bernard, 2016/04/17
Re:Lilypond error behaviour, Peter Gentry, 2016/04/17
Re: Lilypond error behaviour, Johannes Waldmann, 2016/04/18