Zeev Suraski <[EMAIL PROTECTED]> wrote... : > They should definitely be in the C code. Look at gettext as a pretty good > example. > Taking them out is seriously inferior to having them in - it makes > maintenance much tougher, and PHP itself less robust. Suddenly, if you > don't have some external file, errors would show up as stupid error > numbers. What are we looking forward to? Having something like "Error > 29871" and then having to look up error 29871 and seeing it means "Unable > to find external error message database"?
I think it can be stable enough since once you add an error in code you would add it to the "message database". > No, please. > > About the topic of internationalized error messages in general - I think > the cons outweigh the pros. If we were, however, to ever internationalize > them - it would have to be optional, and with the full hardcoded error > messages inside the code remaining intact. It, of course, would be optional. Set by local setting in php.ini or runtime. -- Maxim Maletsky [EMAIL PROTECTED] -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
