-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error for short array syntax in function call #316
Comments
I'm working on the assumption that these errors are generated due to the parse error that is added by removing the single quote. If that's not the case, please let me know as I'm going to try and work out if that parse error can be caught somewhere. |
I've committed some changes to stop the PHP notices caused by the parse error I was talking about. I now get no errors processing the following code: <?php
class lowerCamelCaseClass
{
public function setSeverity()
{
in_array(
$error->name,
[
AcmeCompany\Core\Error\SecurityException'
]
);
}
} This is the error report:
If I'm fixing the wrong errors, can you please provide me with a gist of the sample code you are using to generate them. |
Thanks for the quick response 👍 It's slightly better - it's not getting caught in a loop! I've boiled it down to the simplest example: I now get this (smaller 😄 )stacktrace...
These are the two errors that are raised:
|
Thanks for providing that code. I've fixed up all errors from all standards for that code. The parse error is going to cause unexpected results in the error report itself, but you shouldn't get any more PHP notices now. But if you find more, please do report them for me. |
Thanks for the quick work 👍 😄 Should save me from having to kill runaway PHP processes! |
…kenizer-split-contextsensitive-test-class Tests/Tokenizer: split `ContextSensitiveKeywordsTest`
I have this function in a class (simplified version of actual code). I'm getting a failure when I remove the apostrophe directly before AcmeCompany.
I'm running
1.5.5
, I have tried1.5.3
and2.0.0RC4
just in case it's a regression or an issue that has already been fixed, but they are also generating errors, they're not identical, but I think it's the same semantic issue.Let me know if you need more information.
Stack trace as follows...
The text was updated successfully, but these errors were encountered: