Nikita Popov

PHP-Parser does not care about the value of the tokens, just that they are defined and distinct from other tokens. It's okay if they get defined by some other library...

Is there still an active interest in fixing this? I could probably do it in the next major version, but wouldn't bother if people have already worked around this anyway.

> I m facing this with PHP 8.1. Is there a plan on fixing this ? Could you please explain in more detail what problem you are seeing and in...

Thanks! This sounds like a bug in PHPCompatibilty to me: While the T_BAD_CHARACTER constant was indeed removed in PHP 7.0, it was added back in PHP 7.4, so if you...

What is the motivation behind exporting the parser generation as part of the public, stable API?

So, I'm mainly concerned about two things: First, the parser generation code is quite tightly coupled to the needs of this project, even with the additional abstraction you've introduced. The...

@m1guelpf There is some relevant news here: We recently ported kmyacc to PHP at https://github.com/ircmaxell/PHP-Yacc, and once it's more mature, this project will switch to using that and remove the...

Closing this as out of scope for this library. Other libraries provide support for this on top of this one, e.g. various static analyzers. https://github.com/ircmaxell/php-cfg is also worth mentioning, which...

The need for traversing arrays stays in any case, as arrays are used for a few more things than just statements. Simple example is the FuncCall node, which has an...

Ah, okay, I have misunderstood your point at first, now I see it. I'll see whether I can add a node for statements without breaking too much stuff.