Re: Re: PEAR_Warning proof of concept

Sergio Carvalho wrote:

I'm definitely against PEAR libraries silencing errors by default, but I don't mind providing that feature to end-users. Not all PHP developers can be PEAR developers, but all PHP developers should be PEAR users.

Well, I just don't like the unconformity of it. New PHP5 libs in PEAR are gonna have to be re-designed anyway (even just to justify new versions). I would say that it's a good opportunity to require good design. Frankly, I've never heard this argument before either. I think Lukas is in the minority if he disables error handling while building even prototype applications. I certainly don't think the demand is great enough to implement such a low-level requirement for the rest of us writing code. That's basically how I see it. Even prototype applications should follow basic design principles and silencing errors using catch() should be very easy to do. I say that unless there is overwhelming popular support for this & some real examples that aren't just bad design, then it's too great a price (non-conformance w/ other PHP5 code). Of course my .02; I just feel strongly about application design & feel strongly about PEAR being a PHP5 team player rather than inventing its own proprietary exception system when PHP5 has it built-in now. Hans