mirror of
https://github.com/php/php-src.git
synced 2024-10-04 00:06:16 +00:00
a98c093d44
RFC 822 *only* supports four digits for the year in order to have a compliant header. RFC 850 supports two digits for the year (y2k_incompliant :) so use that when y2k_compliance is turned off. In either case, both of these formats require that GMT be appended to the header, so we do this as well |
||
---|---|---|
.. | ||
Console | ||
PEAR | ||
scripts | ||
tests | ||
Cache.php | ||
Cache.xml | ||
catalog | ||
CMD.php | ||
CODING_STANDARDS | ||
DB.php | ||
HTTP.php | ||
install-pear.txt | ||
ITX.xml | ||
Log.php | ||
Mail.php | ||
Makefile.in | ||
package.dtd | ||
pear.m4 | ||
PEAR.php | ||
README | ||
System.php | ||
TODO |
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.