Re: code-style - I'm not a big fan of standards that insist on X number of spaces, braces have to be here and here, etc. I don't understand why that needs to be standard when, at the push of a button, my IDE makes the code look exactly the way I want it to look. If you don't have such an IDE, there are lots of independent packages that do it, JRefactory being one of the most interesting (available at sourceforge). The only thing I'd like to see is the use of tabs, so no one has to do anything special to get their spacing right.
That, however, just points out the real problem - having coding standards doesn't automatically make things easier for everyone. It makes things a pain for those who "lose" the debate, and easier for those who win. I'd rather see everyone win. Get yourself a simple code formatter, and use it on files you edit, if you like. Just my $.02. I'm willing to go along with the majority on this and other issues. Conor has a good basic suggestion to everyone - go read all Apache web pages regarding being part of a project. I will probably review them myself now that they'll be more relevant to JMeter. I like the idea of the wiki pages as a good way to preserve an evolving consensus on long range issues. I'd like to recommend that non-long-range issues be made into enhancement requests, as that is also a good way to preserve those ideas. Email, of course, is pretty poor as a way to preserve these ideas. We should make links from JMeter's pages to the JMeter wiki section. -- Michael Stover [EMAIL PROTECTED] Yahoo IM: mstover_ya ICQ: 152975688 AIM: mstover777 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
