Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pike pike
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 104
    • Issues 104
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • pikelang
  • pikepike
  • Issues
  • #2711
Closed
Open
Issue created Jan 24, 2002 by Peter Bortas@zinoOwner

Parse error messages can be confusing

Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=2711

Reported by Martin Stjernholm mast@roxen.com

The define YYERROR_VERBOSE was turned on a while back, to give better error messages for parse errors by listing the expected tokens. Since many productions include TOK_LEX_EOF for error recovery, that token too is considered expected, e.g:

foo.pike:parse error, expecting TOK_LEX_EOF' or '}'' or `')''

The TOK_LEX_EOF bit here is confusing and wrong. Ideally the error reporting code should be overridden to fix this, but it seems like bison doesn't allow that. Perhaps it's better to undefine YYERROR_VERBOSE again.

Assignee
Assign to
Time tracking