The question is: why would your production code have fatal errors? A fatal error occurs because of one of the following reasons:
1) parse error 2) engine instability 3) segfault (well, kinda, its nothing catchable, but it is about as fatal as you can get :) 2 & 3 are very very rare cases, and are almost always bugs in PHP itself. case 1, well, if you've tested your code properly (or at all) you shouldn't be getting this error... I don't get why revising the error scheme (even Maxim's proposal) is really that useful, it seems like a lot of extra work for something that is good enough (i'd say ideal). As for multi-lingual errors, no, no, no, no, no! ohh yeah, and no! I can just imagine the support requests coming to php-general@ (and my private inbox, which unfortunately gets comparable traffic these days) with foreign error strings. Most programming is in english these days, including function names, external libraries, classes, etc. Also, to implement this with any reasonable efficiency, we couldn't use dynamic locales, which will make it quite annoying for external contractors to work on pieces of code. Multi-lingual error codes open's up pandora's box, let's not go there. In conclusion to both (imho):: English is fine. Uncatcheable parse errors is also fine. -Sterling -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
