The Road to 2.1 / 3.0

[Crell]

A new PHP release is coming soon, so it's time to get down and catch up on PER-CS! My expectation is that the next release will be 2.1, not 3.0 (though discussion may shift that).

This is a meta issue to track outstanding tasks for 2.1. We can release 2.1 when everything below has been completed, rejected, or postponed.

Please do NOT discuss details of any of these issues on this thread. Discuss them in their own threads. Only comment here with items that should be added to the consideration list.

New language functionality

• Specify hooks formatting #108
• New PHP 8.4 Syntax: new MyClass()->method() without parentheses #89
• Deprecated attribute #96
• Document how to use aviz #99
• Add section on abbreviation naming #102
• Recommend to always use exit() instead of exit #109

Existing clarifications

• Clarify that php open tags must be lowercase #100
• Add section on abbreviation naming #102
• Remove contradictory statements #103

Proposals

(That something is listed here doesn't mean it will be included, just that we should make a decision on it one way or another before release.)

• Opening brace on new line after return type when argument list is split across multiple lines #94
• Match Expressions operator alignment #92
• Multi import statements allowed? #85

[Crell]

The full list of implemented RFCs for 8.4 is here: https://wiki.php.net/rfc#php_84

I don't think anything other than the items above warrant our attention. If you disagree, suggest something.

[TimWolla]

I don't think anything other than the items above warrant our attention. If you disagree, suggest something.

Looking at https://wiki.php.net/rfc/exit-as-function, it might make sense to recommend always using exit(); with parentheses.

If tools would automatically rewrite this, then code like: https://3v4l.org/KnX6u would not be confusing any more:

<?php

function test(string $param) {
    var_dump($param);
}

define('exit', 'xxx');

test(exit);

[KorvinSzanto]

Edited to add #98

[Crell]

@TimWolla Who in their right mind would write code like that???

If you want to make a PR that requires that, go ahead. I'm not opposed.

[TimWolla]

If you want to make a PR that requires that, go ahead. I'm not opposed.

#109. I have chosen a slightly more reasonably example of how exit() could appear in an expression, where the parenthesis-less form would be confusing.

---

As an aside: Writing that made me wonder if the coding style should have an opinion about the use of function aliases, e.g. join, sizeof, die. Except possibly for die they are almost never used and if they are, they can be confusing.