Add token emulation support for asymmetric visibility modifiers

[8.4] Add support for __PROPERTY__ magic constant

Part of property hooks RFC.

Adjust tests to be compatible with PHPUnit 10 (#998)

This avoids warnings on PHPUnit 10, without actually
switching to PHPUnit 10.

Add missing void return types (#997)

Remove emulation for unsupported PHP versions

Replace startLexing() with tokenize()

For now Lexer::getTokens() still exists, but should probably be
removed.

Move attribute handling into parser

The Lexer now only provides the tokens to the parser, while the
parser is responsible for determining which attributes are placed
on notes. This o

Move attribute handling into parser

The Lexer now only provides the tokens to the parser, while the
parser is responsible for determining which attributes are placed
on notes. This only needs to be done when the attributes are
actually needed, rather than for all tokens.

This removes the usedAttributes lexer option (and lexer options
entirely). The attributes are now enabled unconditionally. They
have less overhead now, and the need to explicitly enable them for
some use cases (e.g. formatting-preserving printing) doesn't seem
like a good tradeoff anymore.

There are some additional changes to the Lexer interface that
should be done after this, and the docs / upgrading guide haven't
been adjusted yet.

show more ...

Adjust tests to work on 32-bit

Fixes #662.

Support readonly before DNF type

This makes us match the PHP 8.2 handling of readonly. Handling of
"readonly" functions is moved to the parser to allow distinguishing
them from reado

Support readonly before DNF type

This makes us match the PHP 8.2 handling of readonly. Handling of
"readonly" functions is moved to the parser to allow distinguishing
them from readonly properties with DNF types. We have to uglify the
grammar to avoid some shift/reduce conflicts. Thank you WordPress.

show more ...

Format tests as well

The unnecessary parentheses for "new" are a bit annoying, but I
can live with it...

Move token mapping from lexer to parser

This allows a different token mapping per parser.

Support readonly as function name

This special case was added after the PHP 8.1 release.

Add support for explicit octal literals

Add emulation for enum keyword

Make keyword emulation check case-insensitive

Correctly handle ?-> in encapsed strings

Followup upstream change.

Emulate PHP 8 attribute syntax

Perform emulation by replacing #[ with %[, then patching % back
to # and coalescing #[ into T_ATTRIBUTE if it is a freestanding
token.

Add support for nullsafe operator

Add reverse emulation support

[PHP 7.4] Add support for numeric literal separators (#615)

Implements RFC https://wiki.php.net/rfc/numeric_literal_separator.

Closes #614.

[PHP 7.4] Add support for arrow functions (#602)

Per RFC https://wiki.php.net/rfc/arrow_functions_v2.

Add support for ??= operator

Introduced in PHP 5.4, represented using an AssignOp\Coalesce node.

updates via "rectorphp/rector" (#573)

- "global" -> remove unused "use" statements
- "phpunit" -> fix "@covers" comments
- "phpunit" -> replace "->will($this->returnValue()" with "->

updates via "rectorphp/rector" (#573)

- "global" -> remove unused "use" statements
- "phpunit" -> fix "@covers" comments
- "phpunit" -> replace "->will($this->returnValue()" with "->willReturn()"
- "UseTest.php" -> add missing namespace
- "composer.json" -> use "autoload-dev"
- remove -> "require_once" usage in the tests (use autoload-dev via composer.json)

-> most of the changes are done automatically by "https://github.com/rectorphp/rector"

show more ...

Make sure heredoc end label not followed by label char

Partial support for flexible heredoc/nowdoc

This only implements the token emulation part, it does not yet
handle the indentation stripping.

Emulating this feature on old PHP ve

Partial support for flexible heredoc/nowdoc

This only implements the token emulation part, it does not yet
handle the indentation stripping.

Emulating this feature on old PHP versions is really tough and is
not going to work perfectly, but hopefully this implementation is
"good enough".

show more ...