[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: brace mismatch in init.ly
From: |
Han-Wen Nienhuys |
Subject: |
Re: brace mismatch in init.ly |
Date: |
Fri, 26 Nov 2004 01:58:30 +0100 |
address@hidden writes:
> Citerar Matthijs Frankena <address@hidden>:
>
> The error messages indicates that there is a problem in your input file
> (missing
> closing bracket or similar).
>
> Hm.. To the hackers: What do you think about adding a new token (lets say EOF,
> invoked with \EOF or similar) which means nothing, just does
>
> lilypond: /* empty */
> | lilypond toplevel_expression {
> }
> | lilypond assignment {
> }
> | lilypond EOF {}
> | lilypond error {
> THIS->error_level_ = 1;
> }
> | lilypond INVALID {
> THIS->error_level_ = 1;
> }
> ;
>
> and then add
> \maininput
> \EOF
> to init.ly? When the input file is incomplete, this would _always_ give an
> error
> like "unexpected EOF", I think. Which might be more intuitive. (may I try to
> write a patch?)
I think we should just remove the "unmatched braces" warning, since
errors will always be caught somewhere else as well. I'm reluctant
about the EOF idea. I think that we should avoid that context errors
point at lily's init files.
--
Han-Wen Nienhuys | address@hidden | http://www.xs4all.nl/~hanwen