[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Tests to assure debug remnants are not in our sources?


Every once in a while, some debug code ends up in a release.

Based on the code that I used to tighten the checks on modules loading correctly, I could quite quickly implement checks to ban certain code sequences. My current idea is to blacklist the following snippets:

"use Carp::Always"
"use Data::Dumper"
"print STDERR"

not to appear in any files in LedgerSMB/, bin/ and LedgerSMB.pm

Any objections?



http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
Ledger-smb-devel mailing list