What Does The Future Hold For PEAR?

14 Apr 2009 | PEAR, PHP

PEAR With PHP 5.3 just over the horizon, I decided to see how well prepared WorkXpress was. Our coding standard is pretty strict and was developed to ensure that our application conforms to E_STRICT standards. However, we all know that some things are inevitably going to fall through the cracks.

The results of my research uncovered a few missed is_a()s and =&s, but for the most part our code was clean. I was pointed to a large amount of code that failed E_STRICT, PEAR. Because PEAR and many of its packages are written in PHP 4, it is missing many things that would make it E_STRICT compliant. Some, but not all, of these are listed below:

Fortunately, PEAR appears to be focusing more on future proofing their code rather than backwards compatibility. Unfortunately, there are still many packages still written in PHP 4 (Mail and Mail_Mime for example). While a visit http://pear.php.net/packages.php?php=5 shows there are 121 PEAR packages written in PHP 5, there are still 314 written in PHP 4. It sounds like PEAR still has a ways to go in order to be E_STRICT compliant.

comments powered by Disqus

Older · View Archive (34)

Add Viddler Videos To Your Drupal Site

Have a Viddler account and looking to embed videos on your website? You could embed the videos directly into the body of your nodes, but that doesn’t give you as much control as you may desire. You could use CCK and the Embedded Media Field (emfield) module, but that doesn’t support Viddler. Or does it?


What's Your Web Service Protocol Of Choice?

I have been doing a lot of web service development at work lately. I completed a FedEx integration for WorkXpress and have been working on a new integration with Drupal. Each of these integrations have involved using both SOAP servers and clients (the client being WorkXpress).