PHP 8 Objects, Patterns, and Practice:

Mastering OO Enhancements, Design

Patterns, and Essential Development
Tools Zandstra
Visit to download the full and correct content document:
https://textbookfull.com/product/php-8-objects-patterns-and-practice-mastering-oo-en
hancements-design-patterns-and-essential-development-tools-zandstra/
More products digital (pdf, epub, mobi) instant
download maybe you interests ...

Biota Grow 2C gather 2C cook Loucas

https://textbookfull.com/product/biota-grow-2c-gather-2c-cook-
loucas/

Mastering PHP design patterns develop robust and

reusable code using a multitude of design patterns for
PHP 7 Ali

https://textbookfull.com/product/mastering-php-design-patterns-
develop-robust-and-reusable-code-using-a-multitude-of-design-
patterns-for-php-7-ali/

Design Patterns in PHP and Laravel 1st Edition Kelt

Dockins

https://textbookfull.com/product/design-patterns-in-php-and-
laravel-1st-edition-kelt-dockins/

MASTERING JAVASCRIPT DESIGN PATTERNS create scalable

and reliable applications with advanced Javascript
design patterns using reliable code 3rd Edition Tomas
Corral Cosas
https://textbookfull.com/product/mastering-javascript-design-
patterns-create-scalable-and-reliable-applications-with-advanced-
javascript-design-patterns-using-reliable-code-3rd-edition-tomas-
Design Patterns by Tutorials Learning design patterns
in Swift 4 2 Joshua Greene

https://textbookfull.com/product/design-patterns-by-tutorials-
learning-design-patterns-in-swift-4-2-joshua-greene/

JavaScript Patterns Build Better Applications with

Coding and Design Patterns 1st Edition Stefanov Stoyan

https://textbookfull.com/product/javascript-patterns-build-
better-applications-with-coding-and-design-patterns-1st-edition-
stefanov-stoyan/

Design Patterns by Tutorials Third Edition Learning

Design Patterns in Swift Raywenderlich Tutorial Team

https://textbookfull.com/product/design-patterns-by-tutorials-
third-edition-learning-design-patterns-in-swift-raywenderlich-
tutorial-team/

Architectural Patterns Uncover essential patterns in

the most indispensable realm of enterprise architecture
1st Edition Pethuru Raj

https://textbookfull.com/product/architectural-patterns-uncover-
essential-patterns-in-the-most-indispensable-realm-of-enterprise-
architecture-1st-edition-pethuru-raj/

Java Design Patterns A tour of 23 gang of four design

patterns in Java 1st Edition Vaskaran Sarcar

https://textbookfull.com/product/java-design-patterns-a-tour-
of-23-gang-of-four-design-patterns-in-java-1st-edition-vaskaran-
sarcar/
Matt Zandstra

PHP 8 Objects, Patterns, and Practice

Mastering OO Enhancements, Design Patterns, and
Essential Development Tools
6th ed.
Matt Zandstra
Brighton, UK

Any source code or other supplementary material referenced by the

author in this book is available to readers on GitHub via the book’s
product page, located at www.​apress.​com/​9781484267905. For more
detailed information, please visit http://​www.​apress.​com/​source-code.

ISBN 978-1-4842-6790-5 e-ISBN 978-1-4842-6791-2

https://doi.org/10.1007/978-1-4842-6791-2

© Matt Zandstra 2021

This work is subject to copyright. All rights are reserved by the

Publisher, whether the whole or part of the material is concerned,
specifically the rights of translation, reprinting, reuse of illustrations,
recitation, broadcasting, reproduction on microfilms or in any other
physical way, and transmission or information storage and retrieval,
electronic adaptation, computer software, or by similar or dissimilar
methodology now known or hereafter developed.

The use of general descriptive names, registered names, trademarks,

service marks, etc. in this publication does not imply, even in the
absence of a specific statement, that such names are exempt from the
relevant protective laws and regulations and therefore free for general
use.

The publisher, the authors and the editors are safe to assume that the
advice and information in this book are believed to be true and accurate
at the date of publication. Neither the publisher nor the authors or the
editors give a warranty, expressed or implied, with respect to the
material contained herein or for any errors or omissions that may have
been made. The publisher remains neutral with regard to jurisdictional
claims in published maps and institutional affiliations.

Distributed to the book trade worldwide by Apress Media, LLC, 1 New

York Plaza, New York, NY 10004, U.S.A. Phone 1-800-SPRINGER, fax
(201) 348-4505, e-mail orders-ny@springer-sbm.com, or visit
www.springeronline.com. Apress Media, LLC is a California LLC and the
sole member (owner) is Springer Science + Business Media Finance Inc
(SSBM Finance Inc). SSBM Finance Inc is a Delaware corporation.
To Louise. Still the whole point.
Introduction
When I first conceived of this book, object-oriented design in PHP was
an esoteric topic. The intervening years have not only seen the
inexorable rise of PHP as an object-oriented language but also the
march of the framework. Frameworks are incredibly useful, of course.
They manage the guts and the glue of many (perhaps, these days, most)
web applications. What’s more, they often exemplify precisely the
principles of design that this book explores.
There is, though, a danger for developers here, as there is in all
useful APIs. This is the fear that one might find oneself relegated to
userland, forced to wait for remote gurus to fix bugs or add features at
their whim. It’s a short step from this standpoint to a kind of exile in
which one is left regarding the innards of a framework as advanced
magic and one’s own work as not much more than a minor adornment
stuck up on top of a mighty unknowable infrastructure.
Although I’m an inveterate reinventor of wheels, the thrust of my
argument is not that we should all throw away our frameworks and
build MVC applications from scratch (at least not always). It is rather
that, as developers, we should understand the problems that
frameworks solve and the strategies they use to solve them. We should
be able to evaluate frameworks not only functionally but in terms of the
design decisions their creators have made and to judge the quality of
their implementations. And yes, when the conditions are right, we
should go ahead and build our own spare and focused applications and,
over time, compile our own libraries of reusable code.
I hope this book goes some way toward helping PHP developers
apply design-oriented insights to their platforms and libraries and
provides some of the conceptual tools needed when it’s time to go it
alone.
Acknowledgments
As always, I have benefited from the support of many people while
working on this edition. But as always, I must also look back to the
book’s origins. I tried out some of this book’s underlying concepts in a
talk in Brighton, back when we were all first marveling at the shiny
possibilities of PHP 5. Thanks to Andy Budd, who hosted the talk, and to
the vibrant Brighton developer community. Thanks also to Jessey
White-Cinis, who was at that meeting and who put me in touch with
Martin Streicher at Apress.
Once again, this time around, the Apress team has provided
enormous support, feedback, and encouragement. I am lucky to have
benefited from such professionalism.
I’m very lucky to have had my friend and colleague, Paul Tregoing,
working on this edition as Technical Reviewer. The fact that PHP itself
was under active development throughout the writing of this book
demanded extra vigilance. Code examples that were perfectly valid in
early drafts were rendered incorrect by the language’s fast evolution.
Once again, this edition has greatly benefited from Paul’s knowledge,
insight, and attention to detail—many thanks Paul!
Thanks and love to my wife, Louise. The production of this book has
coincided with three pandemic lockdowns, so thanks are also due to
our children, Holly and Jake, for many much-needed distractions—
often provided during Zoom meetings conducted in my office space
(the corner of the kitchen table).
Thanks to Steven Metsker for his kind permission to reimplement in
PHP a simplified version of the parser API he presented in his book,
Building Parsers with Java (Addison-Wesley Professional, 2001).
I write to music, and, in previous editions of this book, I
remembered the great DJ, John Peel, champion of the underground and
the eclectic. The soundtrack for this edition was largely provided by
BBC Radio 3’s contemporary music show, Late Junction, played on a
loop. Thanks to them for keeping things weird.
Table of Contents
Part I: Objects
Chapter 1:​PHP:​Design and Management
The Problem
PHP and Other Languages
About This Book
Objects
Patterns
Practice
What’s New in the Sixth Edition
Summary
Chapter 2:​PHP and Objects
The Accidental Success of PHP Objects
In the Beginning:​PHP/​FI
Syntactic Sugar:​PHP 3
PHP 4 and the Quiet Revolution
Change Embraced:​PHP 5
PHP 7:​Closing the Gap
PHP 8:​The Consolidation Continues
Advocacy and Agnosticism:​The Object Debate
Summary
Chapter 3:​Object Basics
Classes and Objects
A First Class
A First Object (or Two)
Setting Properties in a Class
 Working with Methods
Creating a Constructor Method
Constructor Property Promotion
Default Arguments and Named Arguments
Arguments and Types
Primitive Types
Some Other Type-Checking Functions
Type Declarations:​Object Types
Type Declarations:​Primitive Types
mixed Types
Union Types
Nullable Types
Return Type Declarations
Inheritance
The Inheritance Problem
Working with Inheritance
Public, Private, and Protected:​Managing Access to Your
Classes
Typed Properties
Summary
Chapter 4:​Advanced Features
Static Methods and Properties
Constant Properties
Abstract Classes
Interfaces
Traits
 A Problem for Traits to Solve
Defining and Using a Trait
Using More Than One Trait
Combining Traits and Interfaces
Managing Method Name Conflicts with insteadof
Aliasing Overridden Trait Methods
Using Static Methods in Traits
Accessing Host Class Properties
Defining Abstract Methods in Traits
Changing Access Rights to Trait Methods
Late Static Bindings:​The static Keyword
Handling Errors
Exceptions
Final Classes and Methods
The Internal Error Class
Working with Interceptors
Defining Destructor Methods
Copying Objects with _​_​clone( )
Defining String Values for Your Objects
Callbacks, Anonymous Functions, and Closures
Anonymous Classes
Summary
Chapter 5:​Object Tools
PHP and Packages
PHP Packages and Namespaces
Autoload
 The Class and Object Functions
Looking for Classes
Learning About an Object or Class
Getting a Fully Qualified String Reference to a Class
Learning About Methods
Learning About Properties
Learning About Inheritance
Method Invocation
The Reflection API
Getting Started
Time to Roll Up Your Sleeves
Examining a Class
Examining Methods
Examining Method Arguments
Using the Reflection API
Attributes
Summary
Chapter 6:​Objects and Design
Defining Code Design
Object-Oriented and Procedural Programming
Responsibility
Cohesion
Coupling
Orthogonality
Choosing Your Classes
Polymorphism
 Encapsulation
Forget How to Do It
Four Signposts
Code Duplication
The Class Who Knew Too Much
The Jack of All Trades
Conditional Statements
The UML
Class Diagrams
Sequence Diagrams
Summary
Part II: Patterns
Chapter 7:​What Are Design Patterns?​Why Use Them?​
What Are Design Patterns?​
A Design Pattern Overview
Name
The Problem
The Solution
Consequences
The Gang of Four Format
Why Use Design Patterns?​
A Design Pattern Defines a Problem
A Design Pattern Defines a Solution
Design Patterns Are Language Independent
Patterns Define a Vocabulary
Patterns Are Tried and Tested
 Patterns Are Designed for Collaboration
Design Patterns Promote Good Design
Design Patterns Are Used by Popular Frameworks
PHP and Design Patterns
Summary
Chapter 8:​Some Pattern Principles
The Pattern Revelation
Composition and Inheritance
The Problem
Using Composition
Decoupling
The Problem
Loosening Your Coupling
Code to an Interface, Not to an Implementation
The Concept That Varies
Patternitis
The Patterns
Patterns for Generating Objects
Patterns for Organizing Objects and Classes
Task-Oriented Patterns
Enterprise Patterns
Database Patterns
Summary
Chapter 9:​Generating Objects
Problems and Solutions in Generating Objects
The Singleton Pattern
 The Problem
Implementation
Consequences
Factory Method Pattern
The Problem
Implementation
Consequences
Abstract Factory Pattern
The Problem
Implementation
Consequences
Prototype
The Problem
Implementation
Pushing to the Edge:​Service Locator
Splendid Isolation:​Dependency Injection
The Problem
Implementation
Consequences
Summary
Chapter 10:​Patterns for Flexible Object Programming
Structuring Classes to Allow Flexible Objects
The Composite Pattern
The Problem
Implementation
Consequences
 Composite in Summary
The Decorator Pattern
The Problem
Implementation
Consequences
The Facade Pattern
The Problem
Implementation
Consequences
Summary
Chapter 11:​Performing and Representing Tasks
The Interpreter Pattern
The Problem
Implementation
Interpreter Issues
The Strategy Pattern
The Problem
Implementation
The Observer Pattern
Implementation
The Visitor Pattern
The Problem
Implementation
Visitor Issues
The Command Pattern
The Problem
 Implementation
The Null Object Pattern
The Problem
Implementation
Summary
Chapter 12:​Enterprise Patterns
Architecture Overview
The Patterns
Applications and Layers
Cheating Before We Start
Registry
Implementation
The Presentation Layer
Front Controller
Application Controller
Page Controller
Template View and View Helper
The Business Logic Layer
Transaction Script
Domain Model
Summary
Chapter 13:​Database Patterns
The Data Layer
Data Mapper
The Problem
Implementation
 Consequences
Identity Map
The Problem
Implementation
Consequences
Unit of Work
The Problem
Implementation
Consequences
Lazy Load
The Problem
Implementation
Consequences
Domain Object Factory
The Problem
Implementation
Consequences
The Identity Object
The Problem
Implementation
Consequences
The Selection Factory and Update Factory Patterns
The Problem
Implementation
Consequences
What’s Left of Data Mapper Now?​
 Summary
Part III: Practice
Chapter 14:​Good (and Bad) Practice
Beyond Code
Borrowing a Wheel
Playing Nice
Giving Your Code Wings
Standards
Vagrant
Testing
Continuous Integration
Summary
Chapter 15:​PHP Standards
Why Standards?​
What Are PHP Standards Recommendations?​
Why PSR in Particular?​
Who Are PSRs for?​
Coding with Style
PSR-1 Basic Coding Standard
PSR-12 Extended Coding Style
Checking and Fixing Your Code
PSR-4 Autoloading
The Rules That Matter to Us
Summary
Chapter 16:​PHP Using and Creating Components with Composer
What Is Composer?​
 Installing Composer
Installing a (Set of) Package(s)
Installing a Package from the Command Line
Versions
require-dev
Composer and Autoload
Creating Your Own Package
Adding Package Information
Platform Packages
Distribution Through Packagist
Keeping It Private
Summary
Chapter 17:​Version Control with Git
Why Use Version Control?​
Getting Git
Using an Online Git Repository
Configuring a Git Server
Creating the Remote Repository
Beginning a Project
Cloning the Repository
Updating and Committing
Adding and Removing Files and Directories
Adding a File
Removing a File
Adding a Directory
Removing Directories
 Tagging a Release
Branching a Project
Summary
Chapter 18:​Testing with PHPUnit
Functional Tests and Unit Tests
Testing by Hand
Introducing PHPUnit
Creating a Test Case
Assertion Methods
Testing Exceptions
Running Test Suites
Constraints
Mocks and Stubs
Tests Succeed When They Fail
Writing Web Tests
Refactoring a Web Application for Testing
Simple Web Testing
Introducing Selenium
A Note of Caution
Summary
Chapter 19:​Automated Build with Phing
What Is Phing?​
Getting and Installing Phing
Composing the Build Document
Targets
Properties
 Types
Tasks
Summary
Chapter 20:​Vagrant
The Problem
A Little Setup
Choosing and Installing a Vagrant Box
Mounting Local Directories on the Vagrant Box
Provisioning
Setting Up the Web Server
Setting Up MariaDB
Configuring a Hostname
Wrapping It Up
Summary
Chapter 21:​Continuous Integration
What Is Continuous Integration?​
Preparing a Project for CI
Installing Jenkins Plug-ins
Setting Up the Git Public Key
Installing a Project
Running the First Build
Configuring the Reports
Triggering Builds
Summary
Chapter 22:​Objects, Patterns, Practice
Objects
 Choice
Encapsulation and Delegation
Decoupling
Reusability
Aesthetics
Patterns
What Patterns Buy Us
Patterns and Principles of Design
Practice
Testing
Standards
Version Control
Automated Build
Continuous Integration
What I Missed
Summary
Appendix A:​Bibliography
Books
Articles
Sites
Appendix B:​A Simple Parser
The Scanner
The Parser
Index
About the Author
Matt Zandstra
has worked as a web programmer, consultant, and writer for over two
decades. He is the author of SAMS Teach Yourself PHP in 24 Hours (three
editions) and is a contributor to DHTML Unleashed. He has written
articles for Linux Magazine, Zend, IBM DeveloperWorks, and
php|architect magazine, among others. Matt was a senior
developer/tech lead at Yahoo! and API tech lead at LoveCrafts. Matt
works as a consultant advising companies on their architectures and
system management and also develops systems primarily with PHP and
Java. Matt also writes fiction.
About the Technical Reviewer
Paul Tregoing
has worked in ops and development in a
variety of environments for nearly 20
years. He worked at Yahoo! for 5 years as
a senior developer on the frontpage
team; there he generated his first PHP
using Perl. Other employers include
Bloomberg, Schlumberger, and the
British Antarctic Survey, where he
became intimate with thousands of
penguins.
He now works as a freelance
engineer for various clients, small and
large, building multitiered web apps
using PHP, JavaScript, and many other
technologies. Paul is a voracious
consumer of science fiction and fantasy
and harbors not-so-secret ambitions to try his hand at writing in the
near future. He lives in Cambridge, United Kingdom, with his wife and
children.
Part I
Objects
© Matt Zandstra 2021
M. Zandstra, PHP 8 Objects, Patterns, and Practice
https://doi.org/10.1007/978-1-4842-6791-2_1

1. PHP: Design and Management

Matt Zandstra1
(1) Brighton, UK

In July 2004, PHP 5.0 was released. This version introduced a suite of
radical enhancements. Perhaps first among these was radically
improved support for object-oriented programming. This stimulated
much interest in objects and design within the PHP community. In fact,
this was an intensification of a process that began when version 4 first
made object-oriented programming with PHP a serious reality.
In this chapter, I look at some of the needs that coding with objects
can address. I very briefly summarize some aspects of the evolution of
patterns and related practices.
I also outline the topics covered by this book. I will look at the
following:
The evolution of disaster: A project goes bad
Design and PHP: How object-oriented design techniques took root
in the PHP community
This book: Objects, Patterns, Practice

The Problem
The problem is that PHP is just too easy. It tempts you to try out your
ideas and flatters you with good results. You write much of your code
straight into your web pages, because PHP is designed to support that.
You add utility functions (such as database access code) to files that can
be included from page to page, and before you know it, you have a
working web application.
 You are well on the road to ruin. You don’t realize this, of course,
because your site looks fantastic. It performs well, your clients are
happy, and your users are spending money.
Trouble strikes when you go back to the code to begin a new phase.
Now you have a larger team, some more users, and a bigger budget. Yet,
without warning, things begin to go wrong. It’s as if your project has
been poisoned.
Your new programmer is struggling to understand code that is
second nature to you, although perhaps a little byzantine in its twists
and turns. She is taking longer than you expected to reach full strength
as a team member.
A simple change, estimated at a day, takes three days when you
discover that you must update 20 or more web pages as a result.
One of your coders saves his version of a file over major changes
you made to the same code some time earlier. The loss is not discovered
for three days, by which time you have amended your own local copy. It
takes a day to sort out the mess, holding up a third developer who was
also working on the file.
Because of the application’s popularity, you need to shift the code to
a new server. The project has to be installed by hand, and you discover
that file paths, database names, and passwords are hard-coded into
many source files. You halt work during the move because you don’t
want to overwrite the configuration changes the migration requires.
The estimated two hours becomes eight as it is revealed that someone
did something clever involving the Apache module ModRewrite, and
the application now requires this to operate properly.
You finally launch phase 2. All is well for a day and a half. The first
bug report comes in as you are about to leave the office. The client
phones minutes later to complain. Her report is similar to the first, but
a little more scrutiny reveals that it is a different bug causing similar
behavior. You remember the simple change back at the start of the
phase that necessitated extensive modifications throughout the rest of
the project.
You realize that not all of the required modifications are in place.
This is either because they were omitted to start with or because the
files in question were overwritten in merge collisions. You hurriedly
make the modifications needed to fix the bugs. You’re in too much of a
hurry to test the changes, but they are a simple matter of copy and
paste, so what can go wrong?
The next morning, you arrive at the office to find that a shopping
basket module has been down all night. The last-minute changes you
made omitted a leading quotation mark, rendering the code unusable.
Of course, while you were asleep, potential customers in other time
zones were wide awake and ready to spend money at your store. You fix
the problem, mollify the client, and gather the team for another day’s
firefighting.
This everyday tale of coding folk may seem a little over the top, but I
have seen all these things happen over and over again. Many PHP
projects start their life small and evolve into monsters.
Because the presentation layer also contains application logic,
duplication creeps in early as database queries, authentication checks,
form processing, and more are copied from page to page. Every time a
change is required to one of these blocks of code, it must be made
everywhere that the code is found, or bugs will surely follow.
Lack of documentation makes the code hard to read, and lack of
testing allows obscure bugs to go undiscovered until deployment. The
changing nature of a client’s business often means that code evolves
away from its original purpose until it is performing tasks for which it
is fundamentally unsuited. Because such code has often evolved as a
seething, intermingled lump, it is hard, if not impossible, to switch out
and rewrite parts of it to suit the new purpose.
Now, none of this is bad news if you are a freelance PHP consultant.
Assessing and fixing a system like this can fund expensive espresso
drinks and DVD box sets for six months or more. More seriously,
though, problems of this sort can mean the difference between a
business’s success and failure.

PHP and Other Languages

PHP’s phenomenal popularity meant that its boundaries were tested
early and hard. As you will see in the next chapter, PHP started life as a
set of macros for managing personal home pages. With the advent of
PHP 3 and, to a greater extent, PHP 4, the language rapidly became the
successful power behind large enterprise websites. In many ways,
however, the legacy of PHP’s beginnings carried through into script
design and project management. In some quarters, PHP retained an
unfair reputation as a hobbyist language, best suited for presentation
tasks.
About this time (around the turn of the millennium), new ideas
were gaining currency in other coding communities. An interest in
object-oriented design galvanized the Java community. Since Java is an
object-oriented language, you may think that this is a redundancy. Java
provides a grain that is easier to work with than against, of course, but
using classes and objects does not in itself determine a particular
design approach.
The concept of the design pattern as a way of describing a problem,
together with the essence of its solution, was first discussed in the
1970s. Perhaps aptly, the idea originated in the field of architecture, not
computer science, in a seminal work by Christopher Alexander: A
Pattern Language (Oxford University Press, 1977). By the early 1990s,
object-oriented programmers were using the same technique to name
and describe problems of software design. The seminal book on design
patterns, Design Patterns: Elements of Reusable Object-Oriented
Software (Addison-Wesley Professional, 1995), by Erich Gamma,
Richard Helm, Ralph Johnson, and John Vlissides (henceforth referred
to in this book by their affectionate nickname, the Gang of Four), is still
indispensable today. The patterns it contains are a required first step
for anyone starting out in this field, which is why most of the patterns
in this book are drawn from it.
The Java language itself deployed many core patterns in its API, but
it wasn’t until the late 1990s that design patterns seeped into the
consciousness of the coding community at large. Patterns quickly
infected the computer sections of Main Street bookstores, and the first
flame wars began on mailing lists and in forums.
Whether you think that patterns are a powerful way of
communicating craft knowledge or largely hot air (and, given the title of
this book, you can probably guess where I stand on that issue), it is
hard to deny that the emphasis on software design they have
encouraged is beneficial in itself.
Related topics also grew in prominence. Among them was Extreme
Programming (XP), championed by Kent Beck. XP is an approach to
Another random document with
no related content on Scribd:
 FOOTNOTES:
[A] Nicely.
[B] Marriage-portion or fortune.
[C] Money.
[D] The megaphone is a speaking-trumpet of great power, the voice from which
can be heard high over the roar of wind or wave fully a mile.
[E] Walrus flesh.
 *** END OF THE PROJECT GUTENBERG EBOOK A LITTLE
GIPSY LASS ***

Updated editions will replace the previous one—the old editions will
be renamed.

Creating the works from print editions not protected by U.S.

copyright law means that no one owns a United States copyright in
these works, so the Foundation (and you!) can copy and distribute it
in the United States without permission and without paying copyright
royalties. Special rules, set forth in the General Terms of Use part of
this license, apply to copying and distributing Project Gutenberg™
electronic works to protect the PROJECT GUTENBERG™ concept
and trademark. Project Gutenberg is a registered trademark, and
may not be used if you charge for an eBook, except by following the
terms of the trademark license, including paying royalties for use of
the Project Gutenberg trademark. If you do not charge anything for
copies of this eBook, complying with the trademark license is very
easy. You may use this eBook for nearly any purpose such as
creation of derivative works, reports, performances and research.
Project Gutenberg eBooks may be modified and printed and given
away—you may do practically ANYTHING in the United States with
eBooks not protected by U.S. copyright law. Redistribution is subject
to the trademark license, especially commercial redistribution.

START: FULL LICENSE

THE FULL PROJECT GUTENBERG LICENSE
 PLEASE READ THIS BEFORE YOU DISTRIBUTE OR USE THIS WORK

To protect the Project Gutenberg™ mission of promoting the free

distribution of electronic works, by using or distributing this work (or
any other work associated in any way with the phrase “Project
Gutenberg”), you agree to comply with all the terms of the Full
Project Gutenberg™ License available with this file or online at
www.gutenberg.org/license.

Section 1. General Terms of Use and

Redistributing Project Gutenberg™
electronic works
1.A. By reading or using any part of this Project Gutenberg™
electronic work, you indicate that you have read, understand, agree
to and accept all the terms of this license and intellectual property
(trademark/copyright) agreement. If you do not agree to abide by all
the terms of this agreement, you must cease using and return or
destroy all copies of Project Gutenberg™ electronic works in your
possession. If you paid a fee for obtaining a copy of or access to a
Project Gutenberg™ electronic work and you do not agree to be
bound by the terms of this agreement, you may obtain a refund from
the person or entity to whom you paid the fee as set forth in
paragraph 1.E.8.

1.B. “Project Gutenberg” is a registered trademark. It may only be

used on or associated in any way with an electronic work by people
who agree to be bound by the terms of this agreement. There are a
few things that you can do with most Project Gutenberg™ electronic
works even without complying with the full terms of this agreement.
See paragraph 1.C below. There are a lot of things you can do with
Project Gutenberg™ electronic works if you follow the terms of this
agreement and help preserve free future access to Project
Gutenberg™ electronic works. See paragraph 1.E below.
1.C. The Project Gutenberg Literary Archive Foundation (“the
Foundation” or PGLAF), owns a compilation copyright in the
collection of Project Gutenberg™ electronic works. Nearly all the
individual works in the collection are in the public domain in the
United States. If an individual work is unprotected by copyright law in
the United States and you are located in the United States, we do
not claim a right to prevent you from copying, distributing,
performing, displaying or creating derivative works based on the
work as long as all references to Project Gutenberg are removed. Of
course, we hope that you will support the Project Gutenberg™
mission of promoting free access to electronic works by freely
sharing Project Gutenberg™ works in compliance with the terms of
this agreement for keeping the Project Gutenberg™ name
associated with the work. You can easily comply with the terms of
this agreement by keeping this work in the same format with its
attached full Project Gutenberg™ License when you share it without
charge with others.

1.D. The copyright laws of the place where you are located also
govern what you can do with this work. Copyright laws in most
countries are in a constant state of change. If you are outside the
United States, check the laws of your country in addition to the terms
of this agreement before downloading, copying, displaying,
performing, distributing or creating derivative works based on this
work or any other Project Gutenberg™ work. The Foundation makes
no representations concerning the copyright status of any work in
any country other than the United States.

1.E. Unless you have removed all references to Project Gutenberg:

1.E.1. The following sentence, with active links to, or other

immediate access to, the full Project Gutenberg™ License must
appear prominently whenever any copy of a Project Gutenberg™
work (any work on which the phrase “Project Gutenberg” appears, or
with which the phrase “Project Gutenberg” is associated) is
accessed, displayed, performed, viewed, copied or distributed:
 This eBook is for the use of anyone anywhere in the United
States and most other parts of the world at no cost and with
almost no restrictions whatsoever. You may copy it, give it away
or re-use it under the terms of the Project Gutenberg License
included with this eBook or online at www.gutenberg.org. If you
are not located in the United States, you will have to check the
laws of the country where you are located before using this
eBook.

1.E.2. If an individual Project Gutenberg™ electronic work is derived

from texts not protected by U.S. copyright law (does not contain a
notice indicating that it is posted with permission of the copyright
holder), the work can be copied and distributed to anyone in the
United States without paying any fees or charges. If you are
redistributing or providing access to a work with the phrase “Project
Gutenberg” associated with or appearing on the work, you must
comply either with the requirements of paragraphs 1.E.1 through
1.E.7 or obtain permission for the use of the work and the Project
Gutenberg™ trademark as set forth in paragraphs 1.E.8 or 1.E.9.

1.E.3. If an individual Project Gutenberg™ electronic work is posted

with the permission of the copyright holder, your use and distribution
must comply with both paragraphs 1.E.1 through 1.E.7 and any
additional terms imposed by the copyright holder. Additional terms
will be linked to the Project Gutenberg™ License for all works posted
with the permission of the copyright holder found at the beginning of
this work.

1.E.4. Do not unlink or detach or remove the full Project

Gutenberg™ License terms from this work, or any files containing a
part of this work or any other work associated with Project
Gutenberg™.

1.E.5. Do not copy, display, perform, distribute or redistribute this

electronic work, or any part of this electronic work, without
prominently displaying the sentence set forth in paragraph 1.E.1 with
active links or immediate access to the full terms of the Project
Gutenberg™ License.
1.E.6. You may convert to and distribute this work in any binary,
compressed, marked up, nonproprietary or proprietary form,
including any word processing or hypertext form. However, if you
provide access to or distribute copies of a Project Gutenberg™ work
in a format other than “Plain Vanilla ASCII” or other format used in
the official version posted on the official Project Gutenberg™ website
(www.gutenberg.org), you must, at no additional cost, fee or expense
to the user, provide a copy, a means of exporting a copy, or a means
of obtaining a copy upon request, of the work in its original “Plain
Vanilla ASCII” or other form. Any alternate format must include the
full Project Gutenberg™ License as specified in paragraph 1.E.1.

1.E.7. Do not charge a fee for access to, viewing, displaying,

performing, copying or distributing any Project Gutenberg™ works
unless you comply with paragraph 1.E.8 or 1.E.9.

1.E.8. You may charge a reasonable fee for copies of or providing

access to or distributing Project Gutenberg™ electronic works
provided that:

• You pay a royalty fee of 20% of the gross profits you derive from
the use of Project Gutenberg™ works calculated using the
method you already use to calculate your applicable taxes. The
fee is owed to the owner of the Project Gutenberg™ trademark,
but he has agreed to donate royalties under this paragraph to
the Project Gutenberg Literary Archive Foundation. Royalty
payments must be paid within 60 days following each date on
which you prepare (or are legally required to prepare) your
periodic tax returns. Royalty payments should be clearly marked
as such and sent to the Project Gutenberg Literary Archive
Foundation at the address specified in Section 4, “Information
about donations to the Project Gutenberg Literary Archive
Foundation.”

• You provide a full refund of any money paid by a user who

notifies you in writing (or by e-mail) within 30 days of receipt that
s/he does not agree to the terms of the full Project Gutenberg™
License. You must require such a user to return or destroy all
 copies of the works possessed in a physical medium and
discontinue all use of and all access to other copies of Project
Gutenberg™ works.

• You provide, in accordance with paragraph 1.F.3, a full refund of

any money paid for a work or a replacement copy, if a defect in
the electronic work is discovered and reported to you within 90
days of receipt of the work.

• You comply with all other terms of this agreement for free
distribution of Project Gutenberg™ works.

1.E.9. If you wish to charge a fee or distribute a Project Gutenberg™

electronic work or group of works on different terms than are set
forth in this agreement, you must obtain permission in writing from
the Project Gutenberg Literary Archive Foundation, the manager of
the Project Gutenberg™ trademark. Contact the Foundation as set
forth in Section 3 below.

1.F.

1.F.1. Project Gutenberg volunteers and employees expend

considerable effort to identify, do copyright research on, transcribe
and proofread works not protected by U.S. copyright law in creating
the Project Gutenberg™ collection. Despite these efforts, Project
Gutenberg™ electronic works, and the medium on which they may
be stored, may contain “Defects,” such as, but not limited to,
incomplete, inaccurate or corrupt data, transcription errors, a
copyright or other intellectual property infringement, a defective or
damaged disk or other medium, a computer virus, or computer
codes that damage or cannot be read by your equipment.

1.F.2. LIMITED WARRANTY, DISCLAIMER OF DAMAGES - Except

for the “Right of Replacement or Refund” described in paragraph
1.F.3, the Project Gutenberg Literary Archive Foundation, the owner
of the Project Gutenberg™ trademark, and any other party
distributing a Project Gutenberg™ electronic work under this
agreement, disclaim all liability to you for damages, costs and
expenses, including legal fees. YOU AGREE THAT YOU HAVE NO
REMEDIES FOR NEGLIGENCE, STRICT LIABILITY, BREACH OF
WARRANTY OR BREACH OF CONTRACT EXCEPT THOSE
PROVIDED IN PARAGRAPH 1.F.3. YOU AGREE THAT THE
FOUNDATION, THE TRADEMARK OWNER, AND ANY
DISTRIBUTOR UNDER THIS AGREEMENT WILL NOT BE LIABLE
TO YOU FOR ACTUAL, DIRECT, INDIRECT, CONSEQUENTIAL,
PUNITIVE OR INCIDENTAL DAMAGES EVEN IF YOU GIVE
NOTICE OF THE POSSIBILITY OF SUCH DAMAGE.

1.F.3. LIMITED RIGHT OF REPLACEMENT OR REFUND - If you

discover a defect in this electronic work within 90 days of receiving it,
you can receive a refund of the money (if any) you paid for it by
sending a written explanation to the person you received the work
from. If you received the work on a physical medium, you must
return the medium with your written explanation. The person or entity
that provided you with the defective work may elect to provide a
replacement copy in lieu of a refund. If you received the work
electronically, the person or entity providing it to you may choose to
give you a second opportunity to receive the work electronically in
lieu of a refund. If the second copy is also defective, you may
demand a refund in writing without further opportunities to fix the
problem.

1.F.4. Except for the limited right of replacement or refund set forth in
paragraph 1.F.3, this work is provided to you ‘AS-IS’, WITH NO
OTHER WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR ANY PURPOSE.

1.F.5. Some states do not allow disclaimers of certain implied

warranties or the exclusion or limitation of certain types of damages.
If any disclaimer or limitation set forth in this agreement violates the
law of the state applicable to this agreement, the agreement shall be
interpreted to make the maximum disclaimer or limitation permitted
by the applicable state law. The invalidity or unenforceability of any
provision of this agreement shall not void the remaining provisions.
1.F.6. INDEMNITY - You agree to indemnify and hold the
Foundation, the trademark owner, any agent or employee of the
Foundation, anyone providing copies of Project Gutenberg™
electronic works in accordance with this agreement, and any
volunteers associated with the production, promotion and distribution
of Project Gutenberg™ electronic works, harmless from all liability,
costs and expenses, including legal fees, that arise directly or
indirectly from any of the following which you do or cause to occur:
(a) distribution of this or any Project Gutenberg™ work, (b)
alteration, modification, or additions or deletions to any Project
Gutenberg™ work, and (c) any Defect you cause.

Section 2. Information about the Mission of

Project Gutenberg™
Project Gutenberg™ is synonymous with the free distribution of
electronic works in formats readable by the widest variety of
computers including obsolete, old, middle-aged and new computers.
It exists because of the efforts of hundreds of volunteers and
donations from people in all walks of life.

Volunteers and financial support to provide volunteers with the

assistance they need are critical to reaching Project Gutenberg™’s
goals and ensuring that the Project Gutenberg™ collection will
remain freely available for generations to come. In 2001, the Project
Gutenberg Literary Archive Foundation was created to provide a
secure and permanent future for Project Gutenberg™ and future
generations. To learn more about the Project Gutenberg Literary
Archive Foundation and how your efforts and donations can help,
see Sections 3 and 4 and the Foundation information page at
www.gutenberg.org.

Section 3. Information about the Project

Gutenberg Literary Archive Foundation
The Project Gutenberg Literary Archive Foundation is a non-profit
501(c)(3) educational corporation organized under the laws of the
state of Mississippi and granted tax exempt status by the Internal
Revenue Service. The Foundation’s EIN or federal tax identification
number is 64-6221541. Contributions to the Project Gutenberg
Literary Archive Foundation are tax deductible to the full extent
permitted by U.S. federal laws and your state’s laws.

The Foundation’s business office is located at 809 North 1500 West,

Salt Lake City, UT 84116, (801) 596-1887. Email contact links and up
to date contact information can be found at the Foundation’s website
and official page at www.gutenberg.org/contact

Section 4. Information about Donations to

the Project Gutenberg Literary Archive
Foundation
Project Gutenberg™ depends upon and cannot survive without
widespread public support and donations to carry out its mission of
increasing the number of public domain and licensed works that can
be freely distributed in machine-readable form accessible by the
widest array of equipment including outdated equipment. Many small
donations ($1 to $5,000) are particularly important to maintaining tax
exempt status with the IRS.

The Foundation is committed to complying with the laws regulating

charities and charitable donations in all 50 states of the United
States. Compliance requirements are not uniform and it takes a
considerable effort, much paperwork and many fees to meet and
keep up with these requirements. We do not solicit donations in
locations where we have not received written confirmation of
compliance. To SEND DONATIONS or determine the status of
compliance for any particular state visit www.gutenberg.org/donate.

While we cannot and do not solicit contributions from states where

we have not met the solicitation requirements, we know of no
prohibition against accepting unsolicited donations from donors in
such states who approach us with offers to donate.

International donations are gratefully accepted, but we cannot make

any statements concerning tax treatment of donations received from
outside the United States. U.S. laws alone swamp our small staff.

Please check the Project Gutenberg web pages for current donation
methods and addresses. Donations are accepted in a number of
other ways including checks, online payments and credit card
donations. To donate, please visit: www.gutenberg.org/donate.

Section 5. General Information About Project

Gutenberg™ electronic works
Professor Michael S. Hart was the originator of the Project
Gutenberg™ concept of a library of electronic works that could be
freely shared with anyone. For forty years, he produced and
distributed Project Gutenberg™ eBooks with only a loose network of
volunteer support.

Project Gutenberg™ eBooks are often created from several printed

editions, all of which are confirmed as not protected by copyright in
the U.S. unless a copyright notice is included. Thus, we do not
necessarily keep eBooks in compliance with any particular paper
edition.

Most people start at our website which has the main PG search
facility: www.gutenberg.org.

This website includes information about Project Gutenberg™,

including how to make donations to the Project Gutenberg Literary
Archive Foundation, how to help produce our new eBooks, and how
to subscribe to our email newsletter to hear about new eBooks.
back
back
back
back