Aaron Bannert wrote:
On Tue, Oct 22, 2002 at 12:24:17AM -0700, Aaron Bannert wrote:
4) Sharing a build-system will be impossible/painful. Same for a coding standard.
I agree completely. There should be little to no standards in terms of build-systems. Those kinds of decisions are best left up to the implementors. As a Commons PMC member, I am totally against me having any say in the build system of any Commons project. :)
Oops, I forgot to address the coding standard issue. I believe that the ASF has had a loose coding standard for a very long time. It generally comes down to this: no tabs, spaces between () and { }, gratuitous newlines, stuff like that. The link is here (it mostly applies to C, but I can see how it would apply directly to Java/C++/C#/etc..): http://httpd.apache.org/dev/styleguide.html
Loose is good. It increases readability and collaboration without being too strict.
Personally I think a consistent style is important. I'd rather see us all come up with a style that we can agree with rather than everyone using their own. (Keep in mind that the C style is set in stone though, and not by me. :)
Style issues have been (sigh) the source of numerous flamewars at Jakarta. :-(
Because of this, over at the POI site we have tried to avoid these discussions with this resolution: http://jakarta.apache.org/poi/resolutions/res001.html
Personally, I would vote +0 for any proposal, since I use code formatters and work with any type of code.
And BTW, the standard coding guidelines you refer to are nice.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------