Ioan CHIRIAC

Hi @54huige, It's kind from you to help, it's a lot of work, and the parser is still in an alpha release, meaning some nodes may change, new nodes introduced...

Hi, yes actually v3 will not be backward compatible, but changes should be enough simple to implement. Remains some changes to implement before the v3 will be fully released and...

Hi @evilebottnawi and @czosel, interresting approach. In the past I've used https://www.npmjs.com/package/jison but at that time the LR(1) generated code was not good enough to parse some syntax collisions on...

@czosel - better inline support is related to https://github.com/glayzzle/php-parser/issues/170 @evilebottnawi - I'll reverse bad commits, and the php 7.3 https://github.com/glayzzle/php-parser/issues/345 & php 7.4 https://github.com/glayzzle/php-parser/issues/346 are planned on next release ---...

Hi @evilebottnawi , You are registered as collaborator (and also @czosel) from a long time ago, and I already gave you since then the write access level on the repository....

Hi @evilebottnawi, not sure what to do with this PR, can we review it on 3.1 or does it introduce breaking changes ?

Here the problem comes from the way interprets newlines after closing tag (another example of AST oriented for execution). The first "\n" is stripped from the output, a sort of...

I'm agree that creating new nodes does not solves directly your problem, and just fixing the behavior of the inline node would be enough, but here I'm looking for being...

#171 related : removal of `parenthesis` node (replaced with `parenthesizedExpression` property)

related to https://github.com/prettier/plugin-php/issues/517 ```html ``` NB : The `/* ups */` comment would be attached on the script node instead of the inline - I'll try a proposal implementation soon...