Re: Re: other languages

bertrand Gugger wrote:

Errors codes are the only way , in the sense pear delivers general extensions and we cannot quite decide if the message has to be seen and how. (what does not means we shouldn't deliver a standard english for it) However, codes can be number or other, they should be represented by meaningfull constants. But please ! Code must be specific to a package. Did none of you experienced error code messing issued from packages using both the peculiar 1,2,3,... ? If code, not 2 packages should be able to have the same.

Yeah .. for that reason packages must extend PEAR_Error. And this is probably a good time to move the PEAR_Error class into PEAR/Error.php. But remember that I am not talking about error codes only here. Anyways I think we should make it possible and easy for users to plugin their text <-> code mapping, but its beyond the scope of PEAR to provide localized text strings. We would just end with half baked out of sync stuff. regards, Lukas