Re: Re: RFC::Error Handling Guidelines for PHP5 packages

Hans L wrote:

Joshua Eichorn wrote:

For serious PHP5 web applications, I just don't see legacy integration as a huge concern, given that migration is generally fairly quick & easy, and certainly I wouldn't want to have to have both PEAR_Exception and PEAR_Error being used in my app.

You must not be in the process of migrating a serious app then. Changing use of pear_error or whatever your php4 solution was to exceptions takes lots of redesign, coding and testing.

Yes, I wasn't talking about migrating apps; I was talking about migrating PHP4-only PEAR packages for use in my PHP5-only applications. Migrating complex n-tier applications certainly requires application redesign. Migrating single-layer PEAR packages generally does not.

Yes, but... once PEAR packages have been migrated, it will require a redesign of _all_ applications that depend on it. If Greg's solution would be used, it would require minimal changes to applications depending on the package. If the package would be fully migrated to exceptions, it would be a _major_ headache to update a complex application. Klaus