Re: Re: common error handling problem - a PFC issue?

Matthias Nothhaft wrote:

first PEAR_Error should 'throw'/trigger? a user warning/notice? if there is no error code supplied (null?) (while the error code parameter remains optional) -> I think this can be done very soon! A lot of users will wonder about error message which are dedicated for maintainers. This is a good idea, because the maintainers will got lots of mails about fixing :-) On the other side this is bad style.

And what about localizing the real error source for example in situations where an error is passed by an inherited class/object? Give me hint how to implement it, and it will be done ...