Mirrors
/
php
mirror of https://github.com/php/php-src
3
0
Fork 0
Code Releases Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
3869 Commits
541 Branches
1468 Tags
744 MiB
 
 
 
 
 
 
Tree: eefbe904b2
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'eefbe904b2'
${ noResults }
php/pear
Sterling Hughes 3f029b61e8
*** empty log message *** 		26 years ago
..
DB.php PEAR now uses "use" instead of "include". 26 years ago
HTTP.php Avoid E_NOTICE errors in PEAR code. 26 years ago
Makefile.in *** empty log message *** 26 years ago
README @Fix some warnings when compiling in maintainer-mode (Stig) 26 years ago
pear.m4 Integration of -ng changes. Changes: 26 years ago
php-config.in Integration of -ng changes. Changes: 26 years ago
phpextdist Added phpextdist script for making external extension packages. 26 years ago
phpize.in Integration of -ng changes. Changes: 26 years ago

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.