php-src/pear
2002-02-02 00:06:44 +00:00
..
Archive * Adding support of extraction of remote archive http://www/archive.tgz 2002-01-24 08:08:54 +00:00
Console Added readPHPArgv() function that will safely read the $argv PHP array 2002-01-06 20:17:00 +00:00
PEAR * silence warning 2002-01-30 12:18:10 +00:00
scripts * lowercase tags and attributes 2002-01-31 08:19:34 +00:00
tests submit a test that will fail due to php bug #14744 2002-01-11 00:04:55 +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 correct url 2002-01-24 15:02:05 +00:00
DB.php Fix remote security risk, pointed out by Wolfram Kriesing 2002-02-01 16:36:32 +00:00
HTTP.php * Fix bug #15313 2002-01-31 13:41:04 +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
Mail.php call PEAR::raiseError() instead of $this->raiseError() in factory() 2001-12-17 15:33:34 +00:00
Makefile.in * remove broken rule for rebuilding Makefile 2002-01-31 08:19:09 +00:00
package.dtd * add some missing attributes 2002-02-02 00:06:44 +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 Return false when the directory can not be created in mkDir() 2002-01-23 18:53: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/.