php

Developer Dilemmas

Sunday, July 26th, 2009

php-logo

This was a little over an hour worth of my life that I’ll never get back.

During development I run with errors set to E_ALL and turn off error reporting for the live site. Today I thought I would see how E_STRICT would pan out on the framework I use. I knew I would get some new errors so I was already bracing for impact. In PHP6 E_STRICT is to take the place of E_ALL so I figured a Sunday afternoon would be a good time to see what I had in store for me for PHP6.

I try to take advantage of any pear packages I can get a hold of. Pear’s goal is to offer backward compatibility so between some of my own code and pear there was allot of notices. Most of them coming from pear’s use of is_a().

As I looked deeper into into the topic I started to think it was time to move away from PEAR and rethink my framework. Wow, that’s allot of time and allot of work. There are allot of good changes for PHP6. Most of them are reducing the ability to create poorly written scripts.

An hour later I decided I’ll look at this again after PHP6 is stable (could be a while). I don’t why I do this stuff to myself.