php-src/pear
2001-11-15 01:24:35 +00:00
..
Console Add missing loop variable $i. 2001-11-11 04:09:08 +00:00
PEAR implemented "uninstall" command 2001-11-15 01:24:35 +00:00
scripts implemented "uninstall" command 2001-11-15 01:24:35 +00:00
tests * expectError() now accepts "*" as a catch-all 2001-11-04 09:07:17 +00:00
Cache.php 'delete' is a reserved word in Zend Engine 2 2001-08-11 08:08:05 +00:00
Cache.xml - package XML for the Cache 2001-03-29 15:01:16 +00:00
catalog * added sgml/xml catalog file 2001-04-15 23:53:09 +00:00
CMD.php Fixed indentation problems related to use of TAB instead of spaces 2001-02-12 00:38:28 +00:00
CODING_STANDARDS * shame on me ... 2001-11-12 10:52:41 +00:00
DB.php - By default DB_FETCHMODE_OBJECT will do a cast to object from the row 2001-11-08 13:53:44 +00:00
HTTP.php use $HTTP_SERVER_VARS, in case register_globals is Off, and use !empty() 2001-01-31 18:34:39 +00:00
install-pear.txt Complain loudly, if we were not able to install everything. 2000-05-02 22:28:12 +00:00
ITX.xml - Renamed the file following Thies suggestion 2001-03-30 09:16:54 +00:00
Log.php fix the singleton and factory methods for 2001-11-06 21:46:41 +00:00
Mail.php fix multiple factory calls problem with php < 4.0.7 2001-08-09 08:06:52 +00:00
Makefile.in adding PEAR/Registry.php 2001-11-14 09:55:38 +00:00
package.dtd * moved <filelist> from <package> to <release> 2001-10-30 12:08:07 +00:00
pear.m4 @Define HAVE_CONFIG_H when building standalone DSO extensions (Stig) 2001-05-20 05:29:54 +00:00
PEAR.php * expectError() now accepts "*" as a catch-all 2001-11-04 09:07:17 +00:00
README * updated email adress 2001-10-13 09:32:34 +00:00
System.php * moved System.php out of Experimental/ 2001-10-29 12:15:53 +00:00
TODO @PEAR: renamed DB_GETMODE_* to DB_FETCHMODE_*, added setFetchMode() 2000-09-12 00:27:50 +00:00

	   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.