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)
1
Section 1 – PHP 8 OOP
Free Chapter
2
Chapter 1: Object-Oriented PHP
5
Section 2 – PHP Types
7
Chapter 5: Object Types, Interfaces, and Unions
9
Section 3 – Clean PHP 8 Patterns and Style
13
Section 4 – PHP 8 Composer Package Management (and PHP 8.1)
16
Section 5 – Bonus Section - PHP 8.1

Never return type

Some functions or methods will never return anything because they do things that will halt execution. Examples of this type of function or method could be methods or functions that throw an exception, or maybe they literally call die or exit to fully halt all execution.

It is worth having a read through the RFC, which is based on the original noreturn type nomenclature:

PHP: rfc:noreturn_type

https://wiki.php.net/rfc/noreturn_type

While these kinds of methods are probably quite rare, it is nice to know that we can now properly assign a return type and that can also be enforced by interfaces and inheritance rules to ensure a consistent API and behavior.

Some scenarios where you might use a never return type are as follows:

  • A throwException method that simply throws an exception and so can never return.
  • An httpRedirect method that issues a 301 HTTP header and then ends execution with exit.
  • A loop method that will loop continuously until...