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

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

За последние 24 часа нас посетили 17172 программиста и 1835 роботов. Сейчас ищут 1543 программиста ...

Оглавление

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

Why PHP?

Вернуться к: System_Daemon

Most daemons are written in C. It's fast & robust. But if you are in a LAMP oriented company like me, and you need to create a lot of software in PHP anyway, it makes sense:

Efficiency. Reuse & connect existing code Think of database connections, classes that create customers from your CRM, etc.
Speed. Deliver new applications very fast PHP has a lot of build in functions that speed up development greatly.
Continuity. Everyone knows PHP (right?) If you work in a small company: chances are there are more PHP programmers than there are C programmers. What if your C guy abandons ship?

Вернуться к: System_Daemon