Lines Matching full:error
100 "syntax error" into languages other than English. The default
117 a syntax error associated with '%token NUM "number"' they might
118 print 'syntax error, unexpected number' instead of 'syntax error,
132 - Error token location.
133 During error recovery, the location of the syntax error is updated
134 to cover the whole sequence covered by the error token: it includes
135 the shifted symbols thrown away during the first part of the error
192 * syntax error processing
194 - In Yacc-style parsers YYLLOC_DEFAULT is now used to compute error
195 locations too. This fixes bugs in error-location computation.
199 discarded during error recovery. This feature is still experimental.
201 - %error-verbose
213 - `parse error' -> `syntax error'
214 Bison now uniformly uses the term `syntax error'; formerly, the code
215 and manual sometimes used the term `parse error' instead. POSIX
216 requires `syntax error' in diagnostics, and it was thought better to
300 but the converse remains an error:
339 * Error token
340 According to POSIX, the error token must be 256.
342 user specified that one of her tokens is numbered 256, then error
345 * Verbose error messages
346 They no longer report `..., expecting error or...' for states where
347 error recovery is possible.
352 * Error recovery now conforms to documentation and to POSIX
353 When a Bison-generated parser encounters a syntax error, it now pops
354 the stack until it finds a state that allows shifting the error
356 allowed some non-error action other than a default reduction on the
357 error token. The new behavior has long been the documented behavior,
359 Paul Eggert, "Reductions during Bison error handling" (2002-05-20)
409 error messages instead of `$end', which remains being the default.
475 fatal error: header and parser would both be named `foo.x'
519 does not trigger an error when the input file is named `plural.y'.
548 * Error messages
549 Some calls to strerror resulted in scrambled or missing error messages.
562 Verbose parse error messages from the parsers are better looking.
563 Before: parse error: unexpected `'/'', expecting `"number"' or `'-'' or `'(''
564 Now: parse error: unexpected '/', expecting "number" or '-' or '('
