Book Image

PHP 7 Programming Blueprints

By : Jose Palala, Martin Helmich
Book Image

PHP 7 Programming Blueprints

By: Jose Palala, Martin Helmich

Overview of this book

When it comes to modern web development, performance is everything. The latest version of PHP has been improvised and updated to make it easier to build for performance, improved engine execution, better memory usage, and a new and extended set of tools. If you’re a web developer, what’s not to love? This guide will show you how to make full use of PHP 7 with a range of practical projects that will not only teach you the principles, but also show you how to put them into practice. It will push and extend your skills, helping you to become a more confident and fluent PHP developer. You’ll find out how to build a social newsletter service, a simple blog with a search capability using Elasticsearch, as well as a chat application. We’ll also show you how to create a RESTful web service, a database class to manage a shopping cart on an e-commerce site and how to build an asynchronous microservice architecture. With further guidance on using reactive extensions in PHP, we’re sure that you’ll find everything you need to take full advantage of PHP 7. So dive in now!
Table of Contents (15 chapters)
PHP 7 Programming Blueprints
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Preface
4
Build a Simple Blog with Search Capability using Elasticsearch

Building a better interface


Right now, the parser that we have built is not really easy to use. In order to use the parser correctly, a user (in this context, read "user" as "another developer that uses your parser") has to call the match_Expr() method (which is just one of many public match_* functions offered by the parser that are not actually supposed to be called by external users), extract the node property from the returned array, and then call the evaluate function on the root node contained in this property. Also, the parser also matches partial strings (remember the example (1 + 2)) * 3, which was recognized as partially correct by our parser), which might really surprise some users.

This reason is enough to extend our project by a new class that encapsulates these quirks and to offer a cleaner interface to our parser. Let's create a new class, Packt\Chp8\DSL\ExpressionBuilder:

namespace Packt\Chp8\DSL\ExpressionBuilder; 
 
use Packt\Chp8\DSL\AST\Expression; 
use Packt\Chp8\DSL\Exception...