lix/tests/functional/lang/parse-fail-eol-2.err.exp

error: undefined variable 'invalid'
       at «stdin»:2:1:
            1| # foo
            2| invalid
             | ^
            3| # bar
match line endings used by parser and error reports the parser treats a plain \r as a newline, error reports do not. this can lead to interesting divergences if anything makes use of this feature, with error reports pointing to wrong locations in the input (or even outside the input altogether). (cherry picked from commit 2be6b143289e5479cc4a2667bb84e879116c2447) Change-Id: Ieb7f7655bac8cb0cf5734c60bd41723388f2973c 2024-01-29 06:19:23 +01:00			`error: undefined variable 'invalid'`
Rename some parse failure tests to `parse-fail-` These were mistakenly labeled `eval-fail-`. Note that the `lang.sh` runner passes `parse-fail-*` tests on stdin, so filenames are removed from error messages. Change-Id: I7f3a0d78b6cfa87af29aaa1b7af19d5a57fd4ade 2024-04-05 00:42:47 +02:00			`at «stdin»:2:1:`
match line endings used by parser and error reports the parser treats a plain \r as a newline, error reports do not. this can lead to interesting divergences if anything makes use of this feature, with error reports pointing to wrong locations in the input (or even outside the input altogether). (cherry picked from commit 2be6b143289e5479cc4a2667bb84e879116c2447) Change-Id: Ieb7f7655bac8cb0cf5734c60bd41723388f2973c 2024-01-29 06:19:23 +01:00			`1\| # foo`
			`2\| invalid`
			`\| ^`
			`3\| # bar`