PHP RFC: Your Title Here

• Version: 0.1
• Date: 2015-02-20
• Author: Thomas Punt, tpunt@hotmail.co.uk
• Status: Draft
• First Published at: http://wiki.php.net/rfc/variadic_empty

This RFC aims to make the empty language construct accept any number of arguments.

// current usage 1:
if (empty($a) || empty($b) || empty($c)) {
    //
}
 
// proposed usage 1:
if (empty($a, $b, $c)) {
    // error here
}
 
// current usage 2:
if (!empty($a) && !empty($b) && !empty($c)) {
    // all good!
}
 
// proposed usage 2:
if (!empty($a, $b, $c)) {
    // all good!
}

By making empty() to accept a variable arity, we can...

What breaks, and what is the justification for it?

List the proposed PHP versions that the feature will be included in. Use relative versions such as “next PHP 5.x” or “next PHP 5.x.y”.

Describe the impact to CLI, Development web server, embedded PHP etc.

Will existing extensions be affected?

It is necessary to develop RFC's with opcache in mind, since opcache is a core extension distributed with PHP.

Please explain how you have verified your RFC's compatibility with opcache.

Describe any new constants so they can be accurately and comprehensively explained in the PHP documentation.

If there are any php.ini settings then list:

• hardcoded default values
• php.ini-development values
• php.ini-production values

Make sure there are no open issues when the vote starts!

List existing areas/features of PHP that will not be changed by the RFC.

This helps avoid any ambiguity, shows that you have thought deeply about the RFC's impact, and helps reduces mail list noise.

This sections details areas where the feature might be improved in future, but that are not currently proposed in this RFC.

Include these so readers know where you are heading and can discuss the proposed voting options.

State whether this project requires a 2/3 or 50%+1 majority (see voting)

Links to any external patches and tests go here.

If there is no patch, make it clear who will create a patch, or whether a volunteer to help with implementation is needed.

Make it clear if the patch is intended to be the final patch, or is just a prototype.

After the project is implemented, this section should contain

1. the version(s) it was merged to
2. a link to the git commit(s)
3. a link to the PHP manual entry for the feature

Links to external references, discussions or RFCs

Keep this updated with features that were discussed on the mail lists.