Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Promote "undefined array key" notice to warning | Nikita Popov | 2020-08-03 | 1 | -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 messages | Máté Kocsis | 2020-07-10 | 1 | -1/+1 |
| | | | | Closes GH-5590 | ||||
* | Change argument error message format | Máté Kocsis | 2020-02-26 | 1 | -1/+1 |
| | | | | Closes GH-5211 | ||||
* | Make type error messages more consistent | Máté Kocsis | 2020-02-17 | 1 | -1/+1 |
| | | | | Closes GH-5092 | ||||
* | Convert some notices to warnings | Nikita Popov | 2019-10-02 | 1 | -1/+1 |
| | | | | Part of https://wiki.php.net/rfc/engine_warnings. | ||||
* | Throw notice on array access on illegal type | Nikita Popov | 2019-07-10 | 1 | -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 Popov | 2016-06-28 | 1 | -0/+18 |
This makes no sense -- SEND_USER can't even handle INDIRECTs. |