You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Christian Stocker fcdd641539 GarbageCollection was moved into a PEAR-Deconstructor 25 years ago
..
Console Use proper class name. 25 years ago
PEAR * updated copyrights (thanks Colin) 26 years ago
scripts * updated copyrights (thanks Colin) 26 years ago
tests @Added raiseError and setErrorHandling methods to PEAR class (Stig, PEAR) 25 years ago
CMD.php Fixed indentation problems related to use of TAB instead of spaces 25 years ago
CODING_STANDARDS Go back to listing the copyright years explicitly (instead of using a 25 years ago
Cache.php GarbageCollection was moved into a PEAR-Deconstructor 25 years ago
DB.php Revised version of the parseDSN function. 25 years ago
HTTP.php use $HTTP_SERVER_VARS, in case register_globals is Off, and use !empty() 25 years ago
Log.php fix the Log::factory() method to assume that the Log stuff is in the 26 years ago
Mail.php factory-generated classes have lowercase subclass names by our (newly 25 years ago
Makefile.in Forgot to add it here 25 years ago
PEAR.php.in * only register the destructor if it exists 25 years ago
README I should learn how to spell 26 years ago
TODO @PEAR: renamed DB_GETMODE_* to DB_FETCHMODE_*, added setFetchMode() 26 years ago
install-pear.txt Complain loudly, if we were not able to install everything. 26 years ago
package.dtd * updated copyrights (thanks Colin) 26 years ago
pear.m4 HEADS UP: renamed config header file in "phpize"d extensions to 25 years ago

README

	   PEAR - PHP Extension and Application Repository
===============================================
Dedicated to Malin Bakken, born 1999-11-21

WHAT IS PEAR?

PEAR is a code repository for PHP extensions and PHP library code
similar to TeX's CTAN and Perl's CPAN.

The intention behind PEAR is to provide a means for library code
authors to organize their code in a defined way shared by other
developers, and to give the PHP community a single source for such
code.


ADMINISTRATION

This section will describe the rules for how files are structured and
how functions and classes should be named.


TOOLS

This section will describe the tools provided to PEAR users.


CODING RULES AND GUIDELINES

* All PHP code must use <?php ?>. This is the only really portable tag.

* Before adding a new top-level directory ("DB" is one), discuss your
intentions on php-pear@lists.php.net.

* Please see the CODING_STANDARDS file for full rules and guidelines.