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
5b0b5b6ed5
php-src/pear
History
Sebastian Bergmann 38933514e1 Update headers.
2001-12-11 15:32:16 +00:00
..
Console Update headers. 2001-12-11 15:32:16 +00:00
PEAR Update headers. 2001-12-11 15:32:16 +00:00
scripts Update headers. 2001-12-11 15:32:16 +00:00
tests * initial commit of PEAR method autoloader 2001-12-10 01:50:11 +00:00
Cache.php Update headers. 2001-12-11 15:32:16 +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 Update headers. 2001-12-11 15:32:16 +00:00
HTTP.php Update headers. 2001-12-11 15:32:16 +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 Update headers. 2001-12-11 15:32:16 +00:00
Makefile.in adding PEAR/Registry.php 2001-11-14 09:55:38 +00:00
package.dtd Update headers. 2001-12-11 15:32:16 +00:00
pear.m4 @Define HAVE_CONFIG_H when building standalone DSO extensions (Stig) 2001-05-20 05:29:54 +00:00
PEAR.php Update headers. 2001-12-11 15:32:16 +00:00
README * updated email adress 2001-10-13 09:32:34 +00:00
System.php Update headers. 2001-12-11 15:32:16 +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 pear-dev@lists.php.net.

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