Skip to content

{ parsing problem #3

@sebbu2

Description

@sebbu2

I tried to compile a (big, c++) project, and got that PARSING error in a standard C++ header:

In state 1138, I expected one of these tokens:
try, {,
/usr/include/c++/4.6/x86_64-linux-gnu/bits/c++config.h:154:1: Parse error (state 1138) at {

I think there is some inconsistencies between the #define in ast and elkhound

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions