Re: [PATCH] Redirect on Error

Derick, that's the price of usability. Open Source always suffered from that, and forever will if the usability will not be considered as one of the main benefits, especially for a programming language as PHP. I agree on 110% that it will be harder to maintain the code. I myself will never use any non-english errors in my PHP setups and will always spend precious minutes grepping for error code. But, this will benefit the whole project. It is not a stupid idea - it is "usability". -- Maxim Maletsky maxim@php.net Derick Rethans <derick@php.net> wrote... : > On Tue, 26 Nov 2002, Maxim Maletsky wrote: > > > marcus.boerger@t-online.de (Marcus Börger) wrote... : > > > > > However i would VERY MUCH appreciate having english error messages hard coded > > > into the source. AND those i18n error messages only activateable by an ini > > > setting. > > > > I disagree. Leaving english comments in C code is obvious, but the > > errors that get printed to user's screens should be out of C code. > > No, I won't want the C code less maintainable and have to search for > error codes all the time. > > > I know, it will hassle some lazy us while coding, but nevertheless, it > > will help documentation ppl to translate errors easlier without knowing > > how extensions are set :) > > It's giving coders more work, work which looks like documenting; and we > all know that coders dont like to document. And being lazy has nothing > to do with it, it's just all practical. Dont forget that most coders > work on PHP because they _need_ the function they are working on in > their jobs. > > Derick > -- > > ------------------------------------------------------------------------- > Derick Rethans > http://derickrethans.nl/ > PHP Magazine - PHP Magazine for Professionals > http://php-mag.net/ > ------------------------------------------------------------------------- > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php >