Skip to content

Conversation

theodorejb
Copy link
Contributor

If a PHP file contains an invalid hex literal such as 0x_10, the expected error
is Parse error: syntax error, unexpected 'x_10' (T_STRING) in %s on line %d.

This already worked correctly on Linux, but on Windows prior to this patch a different
error was produced: Parse error: Invalid numeric literal in %s on line %d.

@theodorejb theodorejb changed the base branch from PHP-7.4 to PHP-7.2 May 9, 2019 19:55
If a PHP file contains an invalid hex literal such as `0x_10`, the expected error
is `Parse error: syntax error, unexpected 'x_10' (T_STRING) in %s on line %d`.

This already worked correctly on Linux, but on Windows prior to this patch a different
error was produced: `Parse error: Invalid numeric literal in %s on line %d`.
@theodorejb theodorejb force-pushed the fix-wrong-parse-error branch from f8d6634 to 3586746 Compare May 9, 2019 22:07
@nikic
Copy link
Member

nikic commented May 13, 2019

Merged as b6b15fc into 7.2+. Thanks!

@nikic nikic closed this May 13, 2019
@theodorejb theodorejb deleted the fix-wrong-parse-error branch May 13, 2019 14:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants