Just before "code freeze" prior to each release, maybe?
-- Salut,
Jordi.
[EMAIL PROTECTED] wrote:
Not that I want to extend a discussion on code formatting standards longer than I have to, but...
It might be best to disallow code formatting via programmatic means (ie, hitting ctrl-shift-F in Eclipse or using pretty printers). The reason is that no matter what standards you decide, applying such tools will create conflicts. I have already seen this with the latest round of formatting.
I like formatting code. I like hitting ctrl-shift-f and seeing everything line up, but if multiple people are really going to work on JMeter, it's not acceptable that everyone will be doing this to files all over. And I think it's unrealistic that people will manually keep their code perfect - who counts the columns while they're typing? We do our best, but code is going to go out of focus eventually.
So, I suggest we disallow the ad hoc use of code formatting tools, and instead, have a regularly scheduled house cleaning that can be done when nobody has uncommitted changes outstanding, and thus avoid conflicts as best we can. The code is put into nice format periodically, and no one ever needs to be browbeaten for not complying exactly - we'll just fix it at the end of the month, or whatever.
-Mike
On 25 Aug 2003 at 0:02, Jeremy Arnold wrote:
Hello,
It looks like people were generally in favor of bumping up the 80 column width limit, but we didn't really make a decision. It can be rather difficult to come to an agreement when we are dealing with
a
sliding scale (80 columns? 100? 120? Personally I prefer
117.5.) So
let's take it one step at a time. We can start with the question:
Should we increase the 80 column width limit for source code
to 100
columns?
If the result is affirmitive, we can then consider further increasing
it
to 120.
My vote for moving to 100 columns is +1.
Jeremy http://xirr.com/~jeremy_a
[EMAIL PROTECTED] wrote:
Can we revisit the rule about 80 column width? Who here is
doing development in a 640x480 environment? I find the waste of vertical space by something like this annoying:
setMethods.add( objectClass.getMethod( "set" + propertyNames[i], new Class[] { propertyClasses[i] }));
80 seems draconian, even for 5 year old monitors. I use 160
generally, and I have no trouble
seeing an entire line (I use 1600x1200 display size). Something
between these two probably
constitutes a happy medium for all of us that conserves both
vertical and horizontal space.
What do people say? Who out there needs an 80 column max?
Can people go to 120 or
higher?
--------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-dev-
[EMAIL PROTECTED]
For additional commands, e-mail: jmeter-dev-
[EMAIL PROTECTED]
-- Michael Stover [EMAIL PROTECTED] Yahoo IM: mstover_ya ICQ: 152975688 AIM: mstover777
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Salut,
Jordi.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
