Peter Donald wrote:
> So I +1 on suggesting standards for external parts of project, -1 for forcing
> it
uh, I jumped in the middle of a "where to place the curly brace code
format pissing contest", how cool.
For those of you who weren't around, we had the first resolution of this
(what later became condensed into the current PMC directives) around
1997 on the jserv-dev mail list. (Jon, remember that?)
Sure, it would be cool to have a clear code convention (or a language
like Python that more or less doesn't even compile if you don't follow
the right conventions) or a benevolent dictator (that used the
convention you like!). Unfortunately, we don't have any of those, so the
resolution was: most of the java source code out there (well, it was
1997, you know!) used the Sun coding conventions so we started from
there, but we decided to be tollerant on *cultural* differences.
And *cultural* differences include: editor used, favorite OS, favorite
mail client, favorite browser, favorite native language, favorite ice
cream flavor... :)
Sure, there should be *compromises* and there are some that are very
useful and understandable (the use of english as the language, no HTML
in email, nice quoting, polite messages, support for old browsers, no
ice cream attached to email) and some that are more subject to personal
judgement (local variable names, curly brace location, tab vs. space,
how many spaces for a tab).
When no objective result can be reached, discussions become religious
wars.
I'd follow Sam suggestions: let's be tollerant.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
