In php5 standard library

[Deevyesh Tyagi]

PHP 5 comes with the Standard PHP Library (SPL), a collection of objects built to handle various tasks such as exception handling and object traversal (iteration). There are basically six groups of cl***es/interfaces available natively to the SPL.

Iterators
Directories
XML
Arrays
Counting
Exceptions
________
LovelyWendie99

[Divyesh]

PEAR-PHP Extension and Application Repository

What is PEAR?
PEAR is short for "PHP Extension and Application Repository" and is pronounced just like the fruit. The purpose of PEAR is to provide:


A structured library of open-sourced code for PHP users

A system for code distribution and package maintenance

A standard style for code written in PHP, specified here

The PHP Extension Community Library (PECL), see more below

A web site, mailing lists and download mirrors to support the PHP/PEAR community


PEAR is a community-driven project with the PEAR Group as the governing body. The project has been founded by Stig S. Bakken in 1999 and quite a lot of people have joined the project since then.

Structured Library of PHP Code
The code in PEAR is partitioned in "packages". Each package is a separate project with its own development team, version number, release cycle, documentation and a defined relation to other packages (including dependencies). Packages are distributed as gzipped tar files with a description file inside, and installed on your local system using the PEAR installer.

There are two types of packages: source packages (containing source files only), and binary packages (containing platform-specific binary files, and possible source files). Installing source packages with C code obviously requires a C build environment.

PEAR defines a package tree, where each "node" in the tree is represented by a part of the package name. The nodes are organized by simple descriptive topics, and each part is separated by an underscore. Examples of package names are "MP3_Id", "Archive_Tar" and "HTTP_Post".

Packages may relate to each other through explicit dependencies, but there is no automatic relation between for example a package and its "parent" in the package tree (for example, "HTTP_Post" is by default independent of "HTTP").
________
F50