PHP Programming Language - Cultural View
PHP Programming Language - Cultural View PHP Programming Language - Cultural View
PEAR 166 PEAR The PHP Extension and Application Repository, or PEAR, is a repository of PHP software code. Stig S. Bakken founded the PEAR project in 1999 to promote the re-use of code that performs common functions. The project seeks to provide a structured library of code, maintain a system for distributing code and for managing code packages, and promote a standard coding style. Though community-driven, the PEAR project has a PEAR Group which serves as the governing body and takes care of administrative tasks. Each PEAR code package comprises an independent project under the PEAR umbrella. It has its own development team, versioning-control and documentation. PEAR packages A PEAR package is distributed as a gzipped tar file. Each archive consists of source code written in PHP, usually in an object-oriented style. Many PEAR packages can readily be used by developers as ordinary third party code via simple include statements in PHP. More elegantly, the PEAR package manager which comes with PHP by default may be used to install PEAR packages so that the extra functionality provided by the package appears as an integrated part of the PHP installation. Unlike the Comprehensive Perl Archive Network (CPAN) archives, which PEAR took as its model, PEAR packages do not have implicit dependencies so that a package's placement in the PEAR package tree does not relate to code dependencies. Rather, PEAR packages must explicitly declare all dependencies on other PEAR packages. The PEAR base classes contain code for simulating object-oriented destructors and consistent error-handling. Packages exist for many basic PHP functions including authentication, caching, database access, encryption, configuration, HTML, web services and XML. PEAR package manager The PEAR package manager provides an easy way to install, uninstall, or upgrade with new PEAR packages or PECL extensions. Before installing a package it can also be instructed to take care of package dependencies so all the extra needed packages are installed too. The PEAR package manager is run from the command line using the pear command. Usually it is therefore only the server administrator who can alter the installed base of PEAR and PECL extensions. On PHP installations running on Linux, the PEAR package manager is ready for usage by default, but on Windows the PEAR package manager is only available after running a batch file called go-pear.bat. PECL PECL (PHP Extension Community Library, pronounced 'pickle') is conceptually very similar to PEAR, and indeed PECL modules are installed with the PEAR Package Manager. PECL contains C extensions for compiling into PHP. As C programs , PECL extensions run more efficiently than PEAR packages. PECL includes modules for XML-parsing, access to additional databases, mail-parsing, embedding Perl or Python in PHP scripts and for compiling PHP scripts. PECL spun off from the PEAR Project in October 2003. Originally it was called the PEAR Extension Code Library, but it now operates independently of PEAR. PECL extensions are documented alongside standard extensions within the PHP Manual, so there is no special manual for PECL extensions. Also, several extensions began their development cycle in PECL and ended up in core (the distributed PHP source) and in many of these cases the PECL versions become unmaintained.
PEAR 167 External links • The PEAR Project [1] • The PEAR Manual [2] • The PECL Project [3] • A PEAR Forum (unofficial) [4] References [1] http://pear.php.net [2] http://pear.php.net/manual/en/ [3] http://pecl.php.net [4] http://www.pear-forum.org/ PHP accelerator A PHP accelerator is an extension designed to boost the performance of software applications written using the PHP programming language. Most PHP accelerators work by caching the compiled bytecode of PHP scripts to avoid the overhead of parsing and compiling source code on each request (some or all of which may never even be executed). For best performance, caching is to shared memory with direct execution from the shared memory and the minimum of memory copying at runtime. A PHP accelerator typically reduces server load and increases the speed of PHP code anywhere from 2–10 times, depending on factors such as the inherent execution time of the PHP application and the percentage of source code actually executed on a given request. While a code optimizer may even slow down overall performance when used in isolation, it can provide an additional performance boost when coupled with a code cache as the optimization effort is performed just once. See also • List of PHP accelerators External links • Benchmarking Drupal with PHP op-code caches: APC, eAccelerator and XCache (and Standard PHP) compared [1] from April 2008. • PHP on Fire: Five Opcode Caches compared [2] including a complete chart [3] featuring Zend Platform, APC, XCache, eAccelerator ionCube Encoder and Standard PHP benchmarks. Made in October 2006. • Alternative PHP Cache [4] available as a PHP extension. References [1] http://2bits.com/articles/benchmarking-drupal-with-php-op-code-caches-apc-eaccelerator-and-xcache-compared.html [2] http://itst.net/654-php-on-fire-three-opcode-caches-compared [3] http://itst.net/wp-content/uploads/2006/10/PHP%20Bytecode%20Cacher%20Review.html [4] http://php.net/manual/en/book.apc.php
- Page 121 and 122: Mambo (software) 115 Mambo (softwar
- Page 123 and 124: Mambo (software) 117 • The former
- Page 125 and 126: Mambo (software) 119 [19] "NYS Depa
- Page 127 and 128: Merlintalk 121 • 2008: Released m
- Page 129 and 130: MetaBB 123 References [1] http://fo
- Page 131 and 132: Midgard (software) 125 Midgard (sof
- Page 133 and 134: Midgard (software) 127 See also •
- Page 135 and 136: Midgard Lite 129 Midgard Lite Midga
- Page 137 and 138: MindTouch Deki 131 History MindTouc
- Page 139 and 140: MindTouch Deki 133 Users of the Com
- Page 141 and 142: Moodle 135 Moodle Moodle course scr
- Page 143 and 144: Moodle 137 show, it has been cited
- Page 145 and 146: Moodle 139 See also • Learning ma
- Page 147 and 148: MyBB 141 MyBB A default installatio
- Page 149 and 150: MyBB 143 free software released und
- Page 151 and 152: NETSOFTWARE 145 Structure of compan
- Page 153 and 154: User:Nichescript/Affiliate Niche Sr
- Page 155 and 156: Ning (website) 149 Feature modifica
- Page 157 and 158: Ning (website) 151 [11] http://blog
- Page 159 and 160: NolaPro 153 In May 2005, NolaPro wa
- Page 161 and 162: ocPortal 155 ocPortal Developer(s)
- Page 163 and 164: ocPortal 157 Version history • Ma
- Page 165 and 166: Open Realty 159 References [1] Open
- Page 167 and 168: Opus (content management system) 16
- Page 169 and 170: osCommerce 163 osCommerce Developer
- Page 171: osCommerce 165 Branches Distributed
- Page 175 and 176: PHP syntax and semantics 169 Colon
- Page 177 and 178: PHP syntax and semantics 171 } { $d
- Page 179 and 180: PHPClasses repository 173 PHPClasse
- Page 181 and 182: PHPDoc 175 markup for display forma
- Page 183 and 184: PHPDoc 177 The text that marks this
- Page 185 and 186: PHPDoc 179 @static Documents a stat
- Page 187 and 188: PHPEclipse 181 Further reading •
- Page 189 and 190: User:Papagel/EFront (eLearning soft
- Page 191 and 192: Phalanger (compiler) 185 Phalanger
- Page 193 and 194: pHAML 187 pHAML Developer(s) David
- Page 195 and 196: pHAML 189 Hello World Hello W
- Page 197 and 198: Phoca Gallery 191 References [1] ht
- Page 199 and 200: PHP 193 PHP Paradigm imperative, ob
- Page 201 and 202: PHP 195 Licensing PHP is free softw
- Page 203 and 204: PHP 197 Security The National Vulne
- Page 205 and 206: PHP 199 $adder = getAdder(8); echo
- Page 207 and 208: PHP 201 Speed optimization PHP sour
- Page 209 and 210: PHP 203 [18] "GoPHP5" (http://gophp
- Page 211 and 212: HipHop for PHP 205 HipHop for PHP D
- Page 213 and 214: PHP-GTK 207 PHP-GTK Developer(s) An
- Page 215 and 216: PHP-GTK 209 External links • Offi
- Page 217 and 218: PHP-Nuke 211 • News—Manages new
- Page 219 and 220: Php4delphi 213 Php4delphi Appeared
- Page 221 and 222: phpDocumentor 215 phpDocumentor Sta
PEAR 166<br />
PEAR<br />
The <strong>PHP</strong> Extension and Application Repository, or PEAR, is a repository of <strong>PHP</strong> software code. Stig S. Bakken<br />
founded the PEAR project in 1999 to promote the re-use of code that performs common functions. The project seeks<br />
to provide a structured library of code, maintain a system for distributing code and for managing code packages, and<br />
promote a standard coding style. Though community-driven, the PEAR project has a PEAR Group which serves as<br />
the governing body and takes care of administrative tasks. Each PEAR code package comprises an independent<br />
project under the PEAR umbrella. It has its own development team, versioning-control and documentation.<br />
PEAR packages<br />
A PEAR package is distributed as a gzipped tar file. Each archive consists of source code written in <strong>PHP</strong>, usually in<br />
an object-oriented style. Many PEAR packages can readily be used by developers as ordinary third party code via<br />
simple include statements in <strong>PHP</strong>. More elegantly, the PEAR package manager which comes with <strong>PHP</strong> by default<br />
may be used to install PEAR packages so that the extra functionality provided by the package appears as an<br />
integrated part of the <strong>PHP</strong> installation. Unlike the Comprehensive Perl Archive Network (CPAN) archives, which<br />
PEAR took as its model, PEAR packages do not have implicit dependencies so that a package's placement in the<br />
PEAR package tree does not relate to code dependencies. Rather, PEAR packages must explicitly declare all<br />
dependencies on other PEAR packages.<br />
The PEAR base classes contain code for simulating object-oriented destructors and consistent error-handling.<br />
Packages exist for many basic <strong>PHP</strong> functions including authentication, caching, database access, encryption,<br />
configuration, HTML, web services and XML.<br />
PEAR package manager<br />
The PEAR package manager provides an easy way to install, uninstall, or upgrade with new PEAR packages or<br />
PECL extensions. Before installing a package it can also be instructed to take care of package dependencies so all<br />
the extra needed packages are installed too.<br />
The PEAR package manager is run from the command line using the pear command. Usually it is therefore only the<br />
server administrator who can alter the installed base of PEAR and PECL extensions. On <strong>PHP</strong> installations running<br />
on Linux, the PEAR package manager is ready for usage by default, but on Windows the PEAR package manager is<br />
only available after running a batch file called go-pear.bat.<br />
PECL<br />
PECL (<strong>PHP</strong> Extension Community Library, pronounced 'pickle') is conceptually very similar to PEAR, and indeed<br />
PECL modules are installed with the PEAR Package Manager. PECL contains C extensions for compiling into <strong>PHP</strong>.<br />
As C programs , PECL extensions run more efficiently than PEAR packages. PECL includes modules for<br />
XML-parsing, access to additional databases, mail-parsing, embedding Perl or Python in <strong>PHP</strong> scripts and for<br />
compiling <strong>PHP</strong> scripts. PECL spun off from the PEAR Project in October 2003. Originally it was called the PEAR<br />
Extension Code Library, but it now operates independently of PEAR.<br />
PECL extensions are documented alongside standard extensions within the <strong>PHP</strong> Manual, so there is no special<br />
manual for PECL extensions. Also, several extensions began their development cycle in PECL and ended up in core<br />
(the distributed <strong>PHP</strong> source) and in many of these cases the PECL versions become unmaintained.