php-src

mirror of https://github.com/php/php-src.git synced 2024-09-22 18:37:25 +00:00

History

Sascha Schumann e53b791b3e Copy header files from main and also add that directory to the list of include directories.		2000-06-14 08:30:37 +00:00
..
DB.php	PEAR now uses "use" instead of "include".	2000-03-09 21:57:14 +00:00
HTTP.php	Avoid E_NOTICE errors in PEAR code.	2000-02-27 14:46:27 +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	Copy header files from main and also add that directory to the list	2000-06-14 08:30:37 +00:00
pear.m4	Use the new PHP_GEN_* macros in pear	2000-06-14 06:30:14 +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 some warnings when compiling in maintainer-mode (Stig)	1999-12-01 22:59:45 +00:00

README

	      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 php4beta@lists.php.net.