clones/php-src
1
0
Fork 0
mirror of https://github.com/php/php-src.git synced 2024-09-22 02:17:32 +00:00
Code Issues Packages Projects Releases Wiki Activity
fc1cdda10d
php-src/pear
History
Sascha Schumann d0c2255750 Fix make install in VPATH builds
2001-01-13 10:02:08 +00:00
..
Console @- Added Console_Getopt class for parsing command-line args. (Andrei, PEAR) 2001-01-11 18:38:26 +00:00
PEAR * updated copyrights (thanks Colin) 2001-01-10 01:01:59 +00:00
scripts * updated copyrights (thanks Colin) 2001-01-10 01:01:59 +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 * updated copyrights (thanks Colin) 2001-01-10 01:01:59 +00:00
HTTP.php * updated copyrights (thanks Colin) 2001-01-10 01:01:59 +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 * updated copyrights (thanks Colin) 2001-01-10 01:01:59 +00:00
Makefile.in Fix make install in VPATH builds 2001-01-13 10:02:08 +00:00
package.dtd * updated copyrights (thanks Colin) 2001-01-10 01:01:59 +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 * updated copyrights (thanks Colin) 2001-01-10 01:01:59 +00:00
README I should learn how to spell 2001-01-09 21:15:26 +00:00
TODO @PEAR: renamed DB_GETMODE_* to DB_FETCHMODE_*, added setFetchMode() 2000-09-12 00:27:50 +00:00

README 

	   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.