php-src/pear
Stig Bakken d400f78079 * expected error codes are stored on a stack now, PEAR::expectError()
pushes into it, PEAR::popExpect() pops off it
* made pear_error test work on other boxes than my own :-)
2001-08-14 21:11:33 +00:00
..
Console
PEAR removed my debug code :) 2001-08-11 16:14:14 +00:00
scripts @Added --version option to php-config (Stig) 2001-08-13 07:58:29 +00:00
tests * expected error codes are stored on a stack now, PEAR::expectError() 2001-08-14 21:11:33 +00:00
Cache.php 'delete' is a reserved word in Zend Engine 2 2001-08-11 08:08:05 +00:00
Cache.xml
catalog
CMD.php
CODING_STANDARDS
DB.php * Added the new fetch row mode: DB_FETCHMODE_OBJECT that returns the columns 2001-08-03 14:13:52 +00:00
HTTP.php
install-pear.txt
ITX.xml
Log.php
Mail.php fix multiple factory calls problem with php < 4.0.7 2001-08-09 08:06:52 +00:00
Makefile.in
package.dtd
pear.m4
PEAR.php * expected error codes are stored on a stack now, PEAR::expectError() 2001-08-14 21:11:33 +00:00
README
TODO

	   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.