On Thu, Jul 31, 2008 at 10:56 PM, Rick Welykochy <[EMAIL PROTECTED]> wrote: > Andrew Moore wrote: > >> On Thu, Jul 31, 2008 at 8:06 AM, Galen Charlton >> <[EMAIL PROTECTED]> wrote: >>> Now imagine what would happen if we (as we should) turn on warnings in >>> Koha. I'll make a proper 3.2 RFC for it shortly, but IMO we really >>> need to start putting in 'use warnings' in a all scripts. Many bugs >>> have already been fixed that were based on undef scalars that should >>> have had a value, and many more undoubtedly lurk. >> >> Hi Galen - >> >> I'm looking forward to that RFC and hearing any resulting discussion. >> At the risk of opening up the discussion too early, I'll say that I'm >> glad to hear that I'm not the only one with that opinion on 'use >> warnings' (and 'use strict'!). > > Enterprise perl (LAMP) apps I have worked on demand the following: > > - "use strict" in every module and script > > - "use warnings" in every module and script > > - during testing: monitor error log(s); there must be ZERO entries written by > the app to the log > and no debug information when going into production How do those apps deal with the 'uninitialized variable' warnings that are so pervasive in Perl apps? 'no warnings uninitialized' perhaps?
Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE CEO migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS [EMAIL PROTECTED] |Full Demos at http://liblime.com/koha |1(888)KohaILS _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
