PHP RFC: Replace "Missing argument" warning with "Too few arguments" exception
- Version: 0.9
- Date: 2016-06-01
- Author: Dmitry Stogov, dmitry@zend.com
- Status: Accepted
- First Published at: https://wiki.php.net/rfc/too_few_args
Introduction
Historically, PHP allows calling functions with fewer actual parameters than required by the function definition. These “non-passed” arguments lead to warning emission and continuation of function execution with uninitialized arguments.
function foo($a) { var_dump($a); // NULL + Warning: Undefined variable: a var_dump($a); // NULL + Warning: Undefined variable: a } foo(); // Warning: Missing argument 1 for foo()
This strange behavior:
- allows execution of functions with unexpected input data (nobody checks isset() for all arguments)
- doesn't have real use cases (in any case, foo($a = null) is better)
- may lead to warning bloating
- disables obvious optimization opportunities
Proposal
I propose to disable calling “user” functions with insufficient actual parameters. PHP will throw an “Error” exception instead.
function foo($a) { var_dump($a); // not executed var_dump($a); // not executed } foo(); // throw Error("Too few arguments to function foo(), 0 passed in %s on line %d and exactly 1 expected")
Using this approach, all attempts to call functions with unexpected input data are going to be caught as soon as possible.
Behavior of internal functions is not going to be changed.
Backward Incompatible Changes
The BC break in intended.
Proposed PHP Version(s)
PHP 7.1
Proposed Voting Choices
The vote is a straight Yes/No vote, that requires a 2/3 majority. The voting began on Jun 6 and will close on Jun 16.
Patches and Tests
Implementation
After the project is implemented, this section should contain
- the version(s) it was merged to
- a link to the git commit ff363e2e7c58353b7e2751d1ca4d7bf616862aae
- a link to the PHP manual entry for the feature