Book Image

The Art of Modern PHP 8

By : Joseph Edmonds
5 (1)
Book Image

The Art of Modern PHP 8

5 (1)
By: Joseph Edmonds

Overview of this book

PHP has come a long way since its introduction. While the language has evolved with PHP 8, there are still a lot of websites running on a version of PHP that is no longer supported. If you are a PHP developer working with legacy PHP systems and want to discover the tenants of modern PHP, this is the book for you. The Art of Modern PHP 8 walks you through the latest PHP features and language concepts. The book helps you upgrade your knowledge of PHP programming and practices. Starting with object-oriented programming (OOP) in PHP and related language features, you'll work through modern programming techniques such as inheritance, understand how it contrasts with composition, and finally look at more advanced language features. You'll learn about the MVC pattern by developing your own MVC system and advance to understanding what a DI container does by building a toy DI container. The book gives you an overview of Composer and how to use it to create reusable PHP packages. You’ll also find techniques for deploying these packages to package libraries for other developers to explore. By the end of this PHP book, you'll have equipped yourself with modern server-side programming techniques using the latest versions of PHP.
Table of Contents (19 chapters)
Section 1 – PHP 8 OOP
Free Chapter
Chapter 1: Object-Oriented PHP
Section 2 – PHP Types
Chapter 5: Object Types, Interfaces, and Unions
Section 3 – Clean PHP 8 Patterns and Style
Section 4 – PHP 8 Composer Package Management (and PHP 8.1)
Section 5 – Bonus Section - PHP 8.1

Coercive and strict modes

Type definitions give our code the guarantee that parameter and return types will be correct. They can operate in two modes. Coercive – the default – is basically as if a manual type cast is called on each parameter at the top of the function, and the return parameter before the variable is returned. This brings back a lot of the type-juggling pain and uncertainty we are trying to avoid.

The other approach, and the one I suggest you use, is strict. In strict mode, PHP will spit its dummy out (throw an exception) at the first sign of your code being misused (by you, no doubt). This early and robust failure allows you to quickly find issues in your code without having to wait for bugs to occur and then figuring out that the cause of the bug is an invalid value being passed further up the call chain.

To enable strict mode, you must include declare(strict_types=1); at the top of your PHP file. You have probably noticed that this is done in...