php-src/pear
Tomas V.V.Cox ed01060897 ws
2002-01-07 00:11:11 +00:00
..
Console Added readPHPArgv() function that will safely read the $argv PHP array 2002-01-06 20:17:00 +00:00
PEAR * support "pear-get install XML_RPC" 2002-01-02 17:12:26 +00:00
scripts use the new Console_Getopt::readPHPArgv() function to read args 2002-01-06 20:19:41 +00:00
tests * PEAR.php line number changes again 2002-01-02 17:19:25 +00:00
Cache.php - included PEAR.php 2001-12-17 11:23:33 +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 Update headers. 2001-12-11 15:32:16 +00:00
CODING_STANDARDS * shame on me ... 2001-11-12 10:52:41 +00:00
DB.php fix phpdoc 2001-12-13 23:07:16 +00:00
HTTP.php ws 2002-01-07 00:11:11 +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 call PEAR::raiseError() instead of $this->raiseError() in factory() 2001-12-17 15:33:34 +00:00
Makefile.in * start splitting "pear" command into "pear" and "pear-get" 2002-01-02 17:11:34 +00:00
package.dtd * added <description> element in <package> 2001-12-28 02:09:27 +00:00
pear.m4 Always output config.nice for standalone extensions. (Really helps with 2001-12-12 20:26:13 +00:00
PEAR.php * Destructors seem to work like a charm. -> No need to keep this line. 2001-12-15 15:01:35 +00:00
README * Add links to the new documentation. 2001-12-15 14:55:02 +00:00
System.php * use "windir" env.var on Windows too 2001-12-26 01:50:08 +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

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

* Please see http://pear.php.net/manual/standards.php for full rules and guidelines.


DOCUMENTATION

Documentation for PEAR can be found at http://pear.php.net/manual/.