Re: [VOTE] space before paren policy

Wow, our first vote-call... ever!

I think this vote-call is premature though. There are at least four
of us that are in favor of something more radical. Peter's ballot
simply addresses the question of, "what should new code look like?"
But Mike Pilato brought up the idea of reformatting *all existing*
code in a single style, and then sticking to that forever:

   "Consistency within a library caters only to the few folks whose
changes are only every to a single library. Those who tackled
problems of any magnitude are going to find themselves working in
multiple libraries, and there goes your consistency...
   I'm with the folks that say consistency across the whole of the
application -- regardless of which style gets chosen as the Golden One
(though I personally much prefer space-before-paren) -- trumps the
half-hearted-yet-wholly-annoying existing policy."

Erik Huelsmann then replied:

   "I'm very much +1 on one consistent style throughout the entire
application. If that means we don't do space-before-paren, that'll be
fine with me."

And then John Peacock said:

   "Having been one of the [non-core] people trying to make changes
across multiple libraries (and getting burned because of it), I'm also
with "JUST PICK SOMETHING!" crowd."

So I wonder if our flowchart should look like this:

VOTE: Should *all* our code be one consistent style? Yes or no.

If "yes" ---> vote on the style. END.

Else if "no" --->

   VOTE: How should new code look?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 28 22:59:41 2006