You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While parting the structure.xml of two projects which are in a EOL stage (they are now embedded in another project), I got the following notice, which lead to a warning and then to a catchable fatal error.
Basically in Parser::getClassDefinitions the variable $classNames gets initialized only inside the loop, but used outside.
By simply adding $classNames = array(); before the loop, all the issues are gone.
I hope this is the only case, as it's not a good habit to use a variable that might be not initialized.
The text was updated successfully, but these errors were encountered:
Definitely not my habit to do that! Frankly this tool was written in a few hours for my own purposes. Not surprising people run into little issues here and there.
While parting the structure.xml of two projects which are in a EOL stage (they are now embedded in another project), I got the following notice, which lead to a warning and then to a catchable fatal error.
Basically in
Parser::getClassDefinitions
the variable$classNames
gets initialized only inside the loop, but used outside.By simply adding
$classNames = array();
before the loop, all the issues are gone.I hope this is the only case, as it's not a good habit to use a variable that might be not initialized.
The text was updated successfully, but these errors were encountered: