The issue

First stable release of PHP version 5 was done two years ago. This version of language has matured a lot throughout these two years and with PHP version 4 development effectively stopped should already be considered the preferred platform by developers of new PHP libraries and applications.

PEAR policies encourage "backwards compatibility", which unfortunately means supporting the inadequate object model of PHP version 4. While it does make sense for existing packages, requiring such "backwards compatibility" for new packages that get accepted into PEAR has at least two problems:

  • It slows the adoption of PHP version 5 by users of PEAR

  • PEAR risks becoming a garbage dump of obsolescent code, or at least be perceived as one

Requiring E_STRICT Compatibility for New PEAR Packages (Previous) The solution (Next)
Last updated: Fri, 19 Sep 2014 — Download Documentation
Do you think that something on this page is wrong? Please file a bug report or add a note.
View this page in:

User Notes:

There are no user contributed notes for this page.