You perhaps are not a veteran of the braces wars of 1973-2011... Please don't try to start them up again!
Every project has its own style. Stick to that style. There is no standard style, Sun's convention is just the style they tried to enforce on their own codebase... I should point out that they didn't enforce it there either. Many a developer was left wounded on the battlefield in those braces wars... let's hope more do not have to follow On 27 January 2012 11:57, bxqdev <bxq...@themailbay.com> wrote: > i guess you mean it's not a constructive question. > it would be, it there wasn't a standard: Sun's Java coding convention, > which already says how to place curly braces correctly. > > why deviate from the de facto standard for no reason? > > thanks. > > > On 1/27/2012 3:48 PM, Stephen Connolly wrote: > >> http://programmers.**stackexchange.com/questions/** >> 2715/should-curly-braces-**appear-on-their-own-line<http://programmers.stackexchange.com/questions/2715/should-curly-braces-appear-on-their-own-line> >> >> On 27 January 2012 11:36, bxqdev<bxq...@themailbay.com> wrote: >> >> Hello, Cassandra Developers! >>> >>> What's the point of the deviation ("important exception") from the Sun's >>> Java coding convention in Cassandra's java code Style: >>> >>> "{ and } are always placed on a new line" >>> >>> Why is that?? >>> >>> thanks. >>> >>> >>
