Lines Matching refs:to

1 Upgrading from PHP-Parser 4.x to 5.0
6 PHP-Parser now requires PHP 7.4 or newer to run. It is however still possible to *parse* code for o…
10 …d. The PHP 7 parser now accepts a `PhpVersion` argument, which can be used to improve compatibilit…
23 …PHP 7 and will cause a parse error. In error recovery mode, it is possible to continue parsing aft…
29 …* The `PhpParser\Parser\Multiple` class has been removed. While not strictly related to PHP 5 supp…
32 ### Changes to the parser factory
36 … if you don't know the PHP version of the code you're parsing. It's better to assume a too new ver…
38  * `createForVersion()`: Use this if you know the PHP version of the code you want to parse.
40 …nd `creatForHostVersion()` are available since PHP-Parser 4.18.0, to allow libraries to support PH…
44 …valid class declaration, while using `public readonly int $prop` will lead to a parse error. Howev…
55 # After (this is roughly equivalent to PREFER_PHP7 behavior)
66 ### Changes to the throw representation
95 ### Changes to the array destructuring representation
148 ### Changes to the name representation
156 It is possible to convert the name to the previous representation using `$name->getParts()`. The
157 `Name` constructor continues to accept both the string and the array representation.
159 The `Name::getParts()` method is available since PHP-Parser 4.16.0, to allow libraries to support
162 ### Changes to the block representation
229 ### Changes to comment assignment
231 Previously, comments were assigned to all nodes starting at the same position. Now they will be
232 assigned to the outermost node only.
296 …r\Modifiers` class, instead of being part of `PhpParser\Node\Stmt\Class_`, to make it clearer that…
309 ### Changes to node constructors
324 ### Changes to the pretty printer
326 …to the standard pretty printer have been made, to make it match contemporary coding style conventi…
392 …h accepts a `PhpVersion` object and defaults to PHP 7.4. The pretty printer will make formatting c…
400 ### Changes to precedence handling in the pretty printer
404 …ifferently in the pretty printer. The internal `p()` method, which is used to recursively print no…
414 …inter methods for operators that participate in precedence resolution need to be adjusted. For exa…
431 The new `$precedence` and `$lhsPrecedence` arguments need to be passed down to the `pInfixOp()`, `p…
433 ### Changes to the node traverser
451 Additionally, the special `NodeVisitor` return values have been moved from `NodeTraverser` to `Node…
460 Visitors can now also be passed directly to the `NodeTraverser` constructor:
471 ### Changes to token representation
491 ### Changes to the lexer
493 The lexer API is reduced to a single `Lexer::tokenize()` method, which returns an array of tokens. …
495 Responsibility for determining start and end attributes for nodes has been moved from the lexer to …
497 There should no longer be a need to directly interact with the `Lexer` for end users, as the `Parse…
533  * `Comment::getReformattedText()` now normalizes CRLF newlines to LF newlines.