I'd say that calls for smarter conflict detection, rather than breaking up code to make conflicts less likely
On Thu, Oct 14, 2010 at 3:01 PM, Josh Berry <[email protected]> wrote: > On Thu, Oct 14, 2010 at 7:48 AM, Reinier Zwitserloot <[email protected]> > wrote: >> For example, method signatures with a lot of parameters tend to grow >> long quickly, but adding a line continuation thoroughly screws up the >> indentation (just think about it - your method signature is a mix of >> indent X and X+2, but the content is all X+1. That really looks weird. >> I tend to include a blank line just to make it a bit less jarring, but >> the problem doesn't go away), and I very very rarely need to read the >> whole thing when I'm reading through code. If I really do need to read >> the whole thing, I'll gladly horizontally scroll (with the keyboard, >> of course). > > > Amusingly, I think this suffers from bad example syndrome. Having > line breaks in method signatures can help with several things, > including merge conflicts. IDEA defaults the indentation of the > parameters to be one higher than what the method body would be, so > maybe I'm breaking another tradition. > > Quickly rereading before I hit send. I'll agree that it could be > "weird." I just think there is a chance it has more benefits than > familiarity. > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
