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.
 
 
 
 
 
 
Tomas V.V.Cox 15f0f8ae23 implemented "uninstall" command 24 years ago
..
Console Add missing loop variable $i. 24 years ago
PEAR implemented "uninstall" command 24 years ago
scripts implemented "uninstall" command 24 years ago
tests * expectError() now accepts "*" as a catch-all 24 years ago
CMD.php Fixed indentation problems related to use of TAB instead of spaces 25 years ago
CODING_STANDARDS * shame on me ... 24 years ago
Cache.php 'delete' is a reserved word in Zend Engine 2 25 years ago
Cache.xml - package XML for the Cache 25 years ago
DB.php - By default DB_FETCHMODE_OBJECT will do a cast to object from the row 24 years ago
HTTP.php use $HTTP_SERVER_VARS, in case register_globals is Off, and use !empty() 25 years ago
ITX.xml - Renamed the file following Thies suggestion 25 years ago
Log.php fix the singleton and factory methods for 24 years ago
Mail.php fix multiple factory calls problem with php < 4.0.7 25 years ago
Makefile.in adding PEAR/Registry.php 24 years ago
PEAR.php * expectError() now accepts "*" as a catch-all 24 years ago
README * updated email adress 24 years ago
System.php * moved System.php out of Experimental/ 24 years ago
TODO @PEAR: renamed DB_GETMODE_* to DB_FETCHMODE_*, added setFetchMode() 26 years ago
catalog * added sgml/xml catalog file 25 years ago
install-pear.txt Complain loudly, if we were not able to install everything. 26 years ago
package.dtd * moved <filelist> from <package> to <release> 24 years ago
pear.m4 @Define HAVE_CONFIG_H when building standalone DSO extensions (Stig) 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 pear-dev@lists.php.net.

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