php-src/pear
Stig Bakken 0f0f1cebcb * new class: PEAR - can be used as a base class for others.
* PEAR_Error moved into PEAR.php to reduce the number of files that are
  always included
* cleaned up the PEAR_Error API a bit and changed the two classes using it
* added PEAR_Installer - an administration class for installing packages
  and maintaining a "class/file cache"
2000-07-24 08:05:51 +00:00
..
PEAR * new class: PEAR - can be used as a base class for others. 2000-07-24 08:05:51 +00:00
DB.php * new class: PEAR - can be used as a base class for others. 2000-07-24 08:05:51 +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
Makefile.in * new class: PEAR - can be used as a base class for others. 2000-07-24 08:05:51 +00:00
pear.in * new class: PEAR - can be used as a base class for others. 2000-07-24 08:05:51 +00:00
pear.m4 Use the new PHP_GEN_* macros in pear 2000-06-14 06:30:14 +00:00
PEAR.php * new class: PEAR - can be used as a base class for others. 2000-07-24 08:05:51 +00:00
php-config.in Copy header files from main and also add that directory to the list 2000-06-14 08:30:37 +00:00
phpextdist Added phpextdist script for making external extension packages. 2000-02-22 14:26:12 +00:00
phpize.in Fix building external extensions. 2000-05-02 20:10:46 +00:00
README Fix this address 2000-07-21 16:39:18 +00:00

	      PEAR - PHP Extension and Add-on 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.