COmanage Developers List

[Marie Huynh <>]

I'm concerned that if I continue to revise the same pieces of code ad nauseam while already behind schedule, we're not going to catch up.  If we're going back to fix old code anyway, why not do it all at the same time and run it through one of these formatters before tagging?

http://coding.smashingmagazine.com/2007/07/12/time-savers-code-beautifier-and-formatter/  

Sure, they won't fix everything, but it's better than doing it all by hand.

On Fri, Dec 16, 2011 at 5:34 AM, Scott Koranda <> wrote:

> On 12/15/11 11:06 PM, Scott Koranda wrote:
> >I do support a consistent and sane coding style, but the
> >length of the document is considerable now, and the detail
> >fine. We have reached the point of diminishing returns.
>
> Are you saying we should revert or that we should stop here?

No, not revert.

I definitely support having a consistent code style and that
we should all follow it as written.

I am saying that it feels comprehensive and evolving it
further makes sense only if it solves a particular
problem--not just for the sake of making it complete with
respect to some metric.

>
> If you compare against the other examples linked, I think we're on
> par in terms of both length and detail.
>

Exactly. So let's use it.

Cheers,

Scott