In this section, you learn some fundamentals and principles that you should apply to PEAR packages that you plan to release.
You can save yourself from some potential trouble by including files wisely. You should follow three principles on including files:
Only use include_once or require_once. Rule number one is to always use require_once or include_once to include PEAR code. If you use require, your script will likely die because of redefinition errors (or it will die sometime in the future).
Determine the correlation between class and file names. PEAR uses the one-class-per-file principle, with the intention that it should be trivial to generate the required file name from the class name. ...