No more off the topic than the discussion on Ruby. At least this one pertains to Tapestry code :) Also, the Jakarta commons coding standard calls for braces on its own line.
-----Original Message----- From: Jamie [mailto:[EMAIL PROTECTED] Sent: Friday, April 22, 2005 3:46 PM To: Tapestry users Subject: Re: If we call it Tapestry 4.0, not 3.x, Maybe we would do much I could give equally compelling arguments as to why having an opening curly brace on its own line is completely stupid, besides the fact that it's way harder (for me) to read (to echo your exclamation, I find this style completely unreadable!), but what's the point? This topic has been argued ad nauseum by proponents of each style forever and there's no point continuing it here. Besides, we've gotten way off topic! How about we get back to Tapestry? Jamie Karthik Abram wrote: > > Oh, and the curly braces should start on the same line... and I like > tabs... 4 character wide... That's the One True Way :) > > > On this one, I STRONGLY disagree. Of the four brace styles (k&r, gnu, bsd, > whitesmith), k&r (which is what Java uses) is the most ridiculous. It makes > the code completely unreadable! By putting the opening brace next to the > control statement, you are making it part of the control statement. It is > not! The language does not dictate that a for loop or a while loop starts > with the for statement and ends with } which is precisely what: > > for (..) { > stmt; > stmt; > } > > makes it look like! > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
