You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It complains about PEGTL\include\tao\pegtl\match.hpp(77,16): error C2065: 'type': undeclared identifier.
I think it has something to do with the unwind change introduced in PEGTL 3.2.6, but no idea. Working in PEGTL 3.2.5
The text was updated successfully, but these errors were encountered:
sephirot47
changed the title
parser_tree.cpp example not compiling in VS 2022, as of PEGTL 2.6
parser_tree.cpp example not compiling in VS 2022, as of PEGTL 2.3.6
Jan 28, 2023
sephirot47
changed the title
parser_tree.cpp example not compiling in VS 2022, as of PEGTL 2.3.6
parser_tree.cpp example not compiling in VS 2022, as of PEGTL 3.2.6
Jan 30, 2023
Yes, I meant 3.2.6 and 3.2.5 xD (I have already edited the issue and message)
I would really love to fix it myself, but the error trace is pretty obscure. I tried but didn't manage to fix it 😞
If the jobs pass, maybe it's something I have misconfigured locally, but I just downloaded and tested the versions without touching anything, and 3.2.5 worked while 3.2.6 & 3.2.7 don't. Sorry I can not help much more with this 😖
I think I may have found the issue, as I experienced it again. Looks like if you have type defined at global scope in your code where parse_tree can see it, MSVC will see this expression at 3.2.7's parse_tree.hpp at line 436:
internal::make_control< Node, Selector, Control >::template type
And not be happy about type there, even though it should be obviously a name under make_control. I guess it is a compiler bug? type might be a silly name to pick at global scope, but I feel like this should work.
It complains about
PEGTL\include\tao\pegtl\match.hpp(77,16): error C2065: 'type': undeclared identifier
.I think it has something to do with the unwind change introduced in PEGTL 3.2.6, but no idea. Working in PEGTL 3.2.5
The text was updated successfully, but these errors were encountered: