summaryrefslogtreecommitdiff
path: root/Zend/tests/call_user_func_007.phpt
Commit message (Collapse)AuthorAgeFilesLines
* Promote "undefined array key" notice to warningNikita Popov2020-08-031-1/+1
| | | | | | | This implements the last remaining part of the https://wiki.php.net/rfc/engine_warnings RFC. Closes GH-5927.
* Review the usage of apostrophes in error messagesMáté Kocsis2020-07-101-1/+1
| | | | Closes GH-5590
* Change argument error message formatMáté Kocsis2020-02-261-1/+1
| | | | Closes GH-5211
* Make type error messages more consistentMáté Kocsis2020-02-171-1/+1
| | | | Closes GH-5092
* Convert some notices to warningsNikita Popov2019-10-021-1/+1
| | | | Part of https://wiki.php.net/rfc/engine_warnings.
* Throw notice on array access on illegal typeNikita Popov2019-07-101-0/+2
| | | | | | | | | | | | | | | No notice is thrown for list() accesses, because we did not come to an agreement regarding patterns like while ([$key, $value] = yield $it->next()) { ... } where silent null access may be desirable. No effort is made to suppress multiple notices in access chains likes $x[0][0][0], because the technical complexity this causes does not seem worthwhile. RFC: https://wiki.php.net/rfc/notice-for-non-valid-array-container
* Don't use FUNC_ARG fetches for call_user_func()Nikita Popov2016-06-281-0/+18
This makes no sense -- SEND_USER can't even handle INDIRECTs.