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.
 
 
 
 
 
 
Stig Bakken 3c801213c6 * updated test (currently passes only on my laptop, sorry...) 25 years ago
..
Console Fix long option parsing. 25 years ago
PEAR removed my debug code :) 25 years ago
scripts @Added --version option to php-config (Stig) 25 years ago
tests * updated test (currently passes only on my laptop, sorry...) 25 years ago
CMD.php Fixed indentation problems related to use of TAB instead of spaces 25 years ago
CODING_STANDARDS Private members don't have to be functions. 25 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 * Added the new fetch row mode: DB_FETCHMODE_OBJECT that returns the columns 25 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 Log::factory() method to assume that the Log stuff is in the 25 years ago
Mail.php fix multiple factory calls problem with php < 4.0.7 25 years ago
Makefile.in Fix for #11821. 25 years ago
PEAR.php * added expectError() method 25 years ago
README I should learn how to spell 25 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 * added LibFile element, used to build Makefile.in 25 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 php-pear@lists.php.net.

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