Re: Minor exception to PEAR coding standard

Daniel, As I just commented on the bug you filed, Agreed this should be an exception. While the dogmatic approach would be to ask Sebastian to change his constant name, the sheer number of user tests that would almost certainly break were he to do so argue convincingly for a legacy-code exception to the rule. (Perhaps a duplicate, all-caps constant could be added, documented and encouraged, with the mixed-case one marked as legacy code that will break in a future non-BC release of PHPUnit?) -- Jeff Dickey Seven Sigma Software and Services Email: jdickey@seven-sigma.com Phone/SMS: +65 8333 4403 Website: http://www.seven-sigma.com/ More contact info: http://card.ly/jdickey > From: Daniel O'Connor <daniel.oconnor@gmail.com> > Date: Mon, 23 Aug 2010 09:14:53 +0930 > To: PEAR Dev <pear-dev@lists.php.net> > Subject: [PEAR-DEV] Minor exception to PEAR coding standard > > *flamesuit on* > http://pear.php.net/bugs/bug.php?id=17798 > > What do we think, people?