Рекурсивный акроним словосочетания «PHP: Hypertext Preprocessor»

Добро пожаловать на форум PHP программистов!

За последние 24 часа нас посетили 17211 программистов и 1834 робота. Сейчас ищут 1624 программиста ...

Оглавление

About the manual Предисловие Basic concepts all PEAR users should understand Installation (Pyrus)Installation (PEAR)Command line installer (PEAR)Dependency Tracking (Meta Packages) with PEAR

Using Pyrus, the PEAR Installer for PHP 5.3+

About Pyrus Commands available in Pyrus Pyrus configuration Differences from the PEAR Installer Creating plugins for Pyrus Developer Tools for Pyrus Using Pyrus in your programs: Pyrus's Public API

PEAR Developer Guide

About PEAR and PEAR2 Becoming a PEAR developer: how to get involved PEAR Developer Guide Coding Standards PEAR Installer: Core components (Installer API, error handling)PEAR Installer: customizing the installer itself RFCs

Channels: distributing your packages

channel.xml, REST, XML-RPC Creating your own channel with Pyrus and PEAR2_SimpleChannelServer

E_STRICT-compatible code

Вернуться к: Стандарты кодирования PEAR

Starting on 01 January 2007, all new code that is suggested for inclusion into PEAR must be E_STRICT-compatible. This means that it must not produce any warnings or errors when PHP's error reporting level is set to E_ALL | E_STRICT.

The development of existing packages that are not E_STRICT-compatible can continue as usual. If however a new major version of the package is released, this major version must then be E_STRICT-compatible.

More details on this part of the Coding Standards can be found in the corresponding RFC.

Вернуться к: Стандарты кодирования PEAR