Fwd: RE: [PHP-PEAR] php4 /pear/Date Calc.php Calendar.php
| From: | Chuck Hagenbuch | Date: | Mon, 16 Oct 2000 15:29:27 +0000 |
| Subject: | Fwd: RE: [PHP-PEAR] php4 /pear/Date Calc.php Calendar.php | ||
| Groups: | php.pear | ||
| Request: | Send a blank email to php-pear+get-389@lists.php.net to get a copy of this message | ||
I think this was supposed to go to the list.
----- Forwarded message from Richard Heyes <richard.heyes@heyes-computing.net>
-----
Date: Mon, 16 Oct 2000 16:27:20 +0100
From: Richard Heyes <richard.heyes@heyes-computing.net>
Reply-To: Richard Heyes <richard.heyes@heyes-computing.net>
Subject: RE: [PHP-PEAR] php4 /pear/Date Calc.php Calendar.php
To: Chuck Hagenbuch <chuck@horde.org>
> If we're going by existing code, then I think the benchmark
> would have to be the
> DB code, since it's probably used in the most places, and
> it's studlyCaps. At
> any rate, at some point we simply have to say "it's fixed,
> we're going with ___"
> and do it, instead of having this discussion every month or
> so. I'm not 100%
> sure we've already reached that point, but I know that _I_
> have a whole lot of
> code that'd break if we changed the DB convention.
My vote would have to go with studlyCaps, even though I prefer not to
use it in my own code, because (as you also say) I have a not
insubstantial amount of code that would break.
Perhaps we should also reach that 100% point because lets face it, the
longer it's left that more code that would potentially have to be
changed if the standard is altered.
My .03p.
--
Richard Heyes
----- End forwarded message -----
-chuck
--
Charles Hagenbuch, <chuck@horde.org>
Many states consider gambling so immoral that they not only prohibit private
gambling organizations, they thoughtfully provide their own.