php-src/pear
Colin Viebrock 4f43188762 I should learn how to spell
PR:
Submitted by:
Reviewed by:
Obtained from:
2001-01-09 21:15:26 +00:00
..
PEAR * display a notice when downloading 2001-01-08 02:54:35 +00:00
tests * added Sebastian's affectedRows() and numRows() for MySQL 2000-12-07 19:53:27 +00:00
CODING_STANDARDS Update the copyright year range to 1997-2001. 2001-01-09 17:42:40 +00:00
DB.php * DB::isManip counts "REPLACE" as a manipulation command (MySQL specific) 2000-12-10 01:32:16 +00:00
HTTP.php various version 2.0 and 2.01 licenses -> 2.02 2000-07-24 05:41:02 +00:00
install-pear.txt Complain loudly, if we were not able to install everything. 2000-05-02 22:28:12 +00:00
Log.php fix the Log::factory() method to assume that the Log stuff is in the 2001-01-04 15:56:05 +00:00
Mail.php revert Jon's patch, leaving only the correct one. 2001-01-05 20:03:01 +00:00
Makefile.in add File/Passwd.php to the install rules, and change the class name to 2001-01-05 20:05:27 +00:00
package.dtd * the beginning of a regression testing framework? 2000-07-25 00:55:37 +00:00
pear.in * updated DB status 2001-01-08 02:45:30 +00:00
pear.m4 PATH is not optional (we print that message, because php-config isn't in the 2000-10-30 18:27:46 +00:00
PEAR.php.in have PEAR::isError() not take parameters by reference for now. 2000-12-04 21:03:17 +00:00
php-config.in fix for Bug id #8606 2001-01-09 07:28:27 +00:00
phpextdist Added phpextdist script for making external extension packages. 2000-02-22 14:26:12 +00:00
phpize.in Add new depend rule to rules_pear.mk and install mkdep.awk. 2000-08-25 07:22:05 +00:00
README I should learn how to spell 2001-01-09 21:15:26 +00:00
run-tests.in @PHP 3 regression testing framework re-born (Stig) 2000-08-27 19:46:06 +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 php-pear@lists.php.net.

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