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.
6076 Commits
543 Branches
1403 Tags
748 MiB
 
 
 
 
 
 
Tree: c6cd319cd4
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'c6cd319cd4'
${ noResults }
php/pear
Sascha Schumann f1ec9035fc
Add new depend rule to rules_pear.mk and install mkdep.awk. 		26 years ago
..
PEAR @Added XML_Parser class in PEAR (Stig) 26 years ago
tests @Added XML_Parser class in PEAR (Stig) 26 years ago
DB.php Remove bogus commit that made DB::DB() an alias for DB::connect() 26 years ago
HTTP.php various version 2.0 and 2.01 licenses -> 2.02 26 years ago
Makefile.in Add new depend rule to rules_pear.mk and install mkdep.awk. 26 years ago
PEAR.php.in -Add getCode() method to PEAR_Error 26 years ago
README * PEAR now stands for "PHP Extension and Application Repository" 26 years ago
TODO added TODO file for PEAR 26 years ago
install-pear.txt Complain loudly, if we were not able to install everything. 26 years ago
package.dtd * the beginning of a regression testing framework? 26 years ago
pear.in * generate pear scripts properly with configure 26 years ago
pear.m4 Use the new PHP_GEN_* macros in pear 26 years ago
php-config.in * generate pear scripts properly with configure 26 years ago
phpextdist Added phpextdist script for making external extension packages. 26 years ago
phpize.in Add new depend rule to rules_pear.mk and install mkdep.awk. 26 years ago
run-tests.in @Added XML_Parser class in PEAR (Stig) 26 years ago

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.