On Wed, Jun 8, 2011 at 2:44 PM, Roger Martín <[email protected]> wrote: > Hi folks: > > I have removed a error in some files. The error consist in: > code (not exact copy) > 1. error_reporting(0); // no error warning > 2. define("AIKI",1); > 3. require_once("aiki.php"); >
That is nasty! > Line 2 define a constants, that or exists or will be create in aiki.files > (the most of cases, generating a error). Aiki don't display any error > because line 1 > sets all errors off... a good politics: make errors but don't show them ;-) > > This is only applicable for files with "direct acces": style.php, > url_widgets.php, etc. > > Other important question is the error_reporting. IMHO is a bad practice > because for developer purpose we must see errors (Don't see it doesnt' mean > it doesn't exist). > Somo people think is best see error during development and hide them in > production..but i prefer see it and make it configurable in each site. > Man it is so great to have a professional code cleaner on our team! Thanks so much for finding and curing these! Jon -- Jon Phillips http://rejon.org/ | http://fabricatorz.com/ chat/skype: kidproto | irc: rejon +1.415.830.3884 (global) | +1-510-499-0894 (sf) +86-187-1003-9974 (beijing) _______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
