readonly<\/code> classes; allow true<\/code>, false<\/code>, and null<\/code> as standalone types; new ways to fetch enums<\/code>; and many more are among them.<\/p>\n\n\n\nThis article will cover most of what’s new, changed, and deprecated in PHP 8.2, from new features and performance improvements to major changes and deprecations.<\/p>\n\n\n
\n\t\t\t\n\t\t\t\tTable of Contents:<\/strong><\/div>\n\t\t\t\t\n\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\n\t\t\t\t- PHP 8.2 for all FastComet Users<\/a><\/li>
- New Features and Improvements in PHP 8.2<\/a>
- New readonly Classes<\/a><\/li>
- Allow true, false, and null as Standalone Types<\/a><\/li>
- Fetch enum Properties in const Expressions<\/a><\/li>
- Disjunctive Normal Form (DNF) Types<\/a><\/li>
- Allow Constants in Traits<\/a><\/li><\/ul><\/li>
- Deprecations in PHP 8.2<\/a><\/li>
- Minor Changes in PHP 8.2<\/a><\/li>
- Additional RFCs in PHP 8.2<\/a><\/li>
- How to Upgrade to PHP 8.2<\/a><\/li>
- Summary<\/a><\/li><\/ul>\n\t\t\t<\/div>\n\t\t<\/div><\/div>\n\n\n
PHP 8.2 for all FastComet Users<\/h2>\n\n\n\n
PHP 8.2 is now available on all FastComet shared servers, and all clients can use the FastComet PHP Selector<\/a> to select it quickly. This is the fastest PHP version yet, so we recommend upgrading if your site is fully compatible. Keep in mind, however, that some plugins may not be compatible with the new version. Remember to thoroughly test your website after upgrading to a new PHP version.<\/p>\n\n\n\nNew Features and Improvements in PHP 8.2<\/h2>\n\n\n\n
Let’s start by going over all of the new PHP 8.2 features. It’s quite a lengthy list:<\/p>\n\n\n\n
New readonly<\/code> Classes<\/h3>\n\n\n\nThe readonly<\/code> feature for class properties was introduced in PHP 8.1<\/a>. PHP 8.2 now includes the ability to declare the entire class as readonly<\/code>.<\/p>\n\n\n\nWhen you declare a class as readonly<\/code>, the readonly<\/code> feature is automatically inherited by all of its properties. Declaring a class readonly<\/code> is equivalent to declaring all class properties readonly<\/code>.<\/p>\n\n\n\nIn PHP 8.1, you had to declare each property as read-only:<\/p>\n\n\n\n
class WorkClassOne
{
public readonly string $ValueA,
public readonly int $ValueB
}<\/pre>\n\n\n\nWith PHP 8.2, you can simply write:<\/p>\n\n\n\n
readonly class WorkClassOne
{
public string $ValueA,
public int $ValueB
}<\/pre>\n\n\n\nYou can now mark abstract or final classes as readonly<\/code>. The order of the keywords is irrelevant here.<\/p>\n\n\n\nabstract readonly class Work {}
final readonly class Home {}<\/pre>\n\n\n\nA readonly<\/code> class with no properties can also be declared. This prevents dynamic properties while allowing child classes to declare their readonly properties explicitly.<\/p>\n\n\n\nSubsequently, classes marked as readonly<\/code> can only possess properties with specified types and the same restriction applies when declaring individual properties as readonly<\/code>. If it is not possible to declare a property with a specific type, then the mixed type property can be utilized.<\/p>\n\n\n\nDeclaring a readonly <\/code>class without a typed property will result in a Fatal error:<\/p>\n\n\n\nreadonly class Work{
public $task;
}
Fatal error: Readonly property Work::$task must have type in \u2026 on line \u2026<\/pre>\n\n\n\nAlso, you cannot declare the following PHP features as readonly<\/code>:<\/p>\n\n\n\n\n- Enums;<\/li>\n\n\n\n
- Traits;<\/li>\n\n\n\n
- Interfaces.<\/li>\n<\/ul>\n\n\n\n
Declaring these features as readonly<\/code> will result in a Parse error.<\/p>\n\n\n\nreadonly trait LoginMessage {}\n\nParse error: syntax error, unexpected token \"trait,\" expecting \"abstract\" or \"final\" or \"readonly\" or \"class\" in ... on line \u2026<\/pre>\n\n\n\nConsidering the behavior of PHP keywords, the readonly<\/code> keyword is case insensitive.<\/p>\n\n\n\nAnother thing to consider is that while dynamic properties are deprecated in this version of PHP, they can still be added to a class. Still if you do it for a readonly<\/code> class that will result in a Fatal Error:<\/p>\n\n\n\nFatal error: Readonly property Work::$task must have type in ... on line ...<\/pre>\n\n\n\nAllow true<\/code>, false<\/code>, and null<\/code> as Standalone Types<\/h3>\n\n\n\nScalar types such as int<\/code>, string<\/code>, and bool<\/code> are already available in PHP. That was expanded upon in PHP 8.0<\/a> with the addition of union types, allowing for different value types. The exact request also permitted the use of false and null as part of a union type but not as standalone types.<\/p>\n\n\n\nA fatal error occurred if you attempted to declare false or null or as standalone types without them being part of a union type.<\/p>\n\n\n\n
PHP 8.2 supports the standalone types false and null to avoid this scenario. PHP’s type system is now more expressive and complete due to this addition. You can now precisely declare the return, parameter, and property types.<\/p>\n\n\n\n
Also, up to PHP 8.1, the programming language still lacks a true type, which is a natural counterpart to the false type. <\/p>\n\n\n\n
PHP 8.2 corrects this and adds support for the true type<\/a>. It does not allow coercion, just as the false type does.<\/p>\n\n\n\nThe true and false types both belong to PHP’s bool type. To eliminate duplication, it is not possible to have all three types declared together in a union type. This will cause a compile-time fatal error.<\/p>\n\n\n\n
Fetch enum<\/code> Properties in const<\/code> Expressions<\/h3>\n\n\n\nThis RFC proposes<\/a> the adoption of the ->\/?-> operator for accessing enum properties in constant expressions. The purpose of this addition is to eliminate the need for duplicating enum values in cases where enum objects cannot be used, such as in array keys.By enabling the retrieval of enum properties in these restricted areas, code can be made more straightforward.<\/p>\n\n\n\nIn addition, there is included support for the null-safe operator ?->.<\/p>\n\n\n\n
Disjunctive Normal Form (DNF) Types<\/h3>\n\n\n\n
The Disjunctive Normal Form (DNF) standardizes the organization of boolean expressions. It is made up of a disjunction of conjunctions \u2014 an OR of ANDs in boolean terms.<\/p>\n\n\n\n
The use of DNF in type declarations provides a consistent way to write combined Union and Intersection types that the parser can handle. The new DNF types<\/a> feature in PHP 8.2 is simple but powerful when used correctly.<\/p>\n\n\n\nAllow Constants in Traits<\/h3>\n\n\n\n
PHP includes a feature called Traits that allows you to reuse code. They’re great for reusing code across classes.<\/p>\n\n\n\n
Currently, only methods and properties can be defined using traits; constants are not supported. In other words, a trait’s expected invariants cannot be defined by the trait itself. To get around this restriction, you must define constants in its composing class or an interface that its composing class implements.<\/p>\n\n\n\n
This RFC proposes<\/a> allowing Traits to define constants. These constants can be defined in the same way that class constants are. This example, taken directly from the RFC, clarifies its application:<\/p>\n\n\n\ntrait Foo
{
public const CONSTANT = 1;
}
class Bar
{
use Foo;
}
var_dump(Bar::CONSTANT); \/\/ 1
var_dump(Foo::CONSTANT); \/\/ Error<\/pre>\n\n\n\nTrait constants, like Trait property and method definitions, are merged into the composing class’s definition. They are also bound by the same rules as trait properties. According to the RFC, while this proposal is a good starting point, more work is needed to flesh out the feature.<\/p>\n\n\n\n
Deprecations in PHP 8.2<\/h2>\n\n\n\n
We can now proceed to the deprecations in PHP 8.2. To be quick, we will provide source links for them:<\/p>\n\n\n\n
\n- Dynamic properties<\/a>;<\/li>\n\n\n\n
- Partially supported callables<\/a>;<\/li>\n\n\n\n
- Both #utf8_encode() and utf8_decode() functions<\/a>;<\/li>\n\n\n\n
- The last two ways of string interpolation<\/a>;<\/li>\n\n\n\n
- The use of mbstring for these encodings<\/a>.<\/li>\n<\/ul>\n\n\n\n
Minor Changes in PHP 8.2<\/h2>\n\n\n\n
Just like with the deprecations, here are some source links with the minor changes in PHP 8.2:<\/p>\n\n\n\n
\n- Remove Support for libmysql from mysqli<\/a>;<\/li>\n\n\n\n
- Locale-Independent Case Conversion<\/a>;<\/li>\n\n\n\n
- Random Extension Improvement<\/a>.<\/li>\n<\/ul>\n\n\n\n
Additional RFCs in PHP 8.2<\/h2>\n\n\n\n
Now with the list of additional RFCs in PHP 8.2:<\/p>\n\n\n\n
\n- New curl_upkeep function<\/a>;<\/li>\n<\/ul>\n\n\n\n
\n- New ini_parse_quantity function<\/a>;<\/li>\n\n\n\n
- New memory_reset_peak_usage function<\/a>;<\/li>\n\n\n\n
- Enable \/n modifier in preg_* functions<\/a>;<\/li>\n\n\n\n
- Make the iterator_*() family accept all iterables<\/a>.<\/li>\n<\/ol>\n\n\n\n
How to Upgrade to PHP 8.2<\/h2>\n\n\n\n
With FastComet\u2019s shared hosting servers, you have the convenient option to select your PHP version<\/a> quickly and easily. All you have to do is:<\/p>\n\n\n\n
![\"Find](\"https:\/\/www.fastcomet.com\/blog\/wp-content\/uploads\/2023\/02\/find-php-selector-in-cpanel-jupiter.png\")
<\/figure>\n\n\n\n![\"Choose](\"https:\/\/www.fastcomet.com\/blog\/wp-content\/uploads\/2023\/02\/choose-php-8-2-in-cpanel.png\")
<\/figure>\n\n\n\n![\"Set](\"https:\/\/www.fastcomet.com\/blog\/wp-content\/uploads\/2023\/02\/set-php-8-2-as-current.png\")
<\/figure>\n\n\n\n