Jeff Verdegan wrote:Obviously there's a lot of personal preference involved here, but I find code easier to read when the lines are long than when a given statement or method call wraps.
Really? I have more problems with statements that have to wrap (OP's method example being a case in point).
Unlike reading a novel, when I read code I don't usually read the whole thing top-to-bottom, left-to-right, beginning-to-end. I tend to read it in chunks--methods, blocks, loops, etc. I'd rather have a single method call with it's multiple or long-named parameters take up a single wide line than wrap to 2 or 3, especially when there are multiple of those in a row.
See above - but given that it might occur (and unfortunately, with things like generics, it often does these days) I don't have any problem with multiple lines (in fact, my Eclipse line limit is 75). Each to his/her own, I guess.
Of course, there's a limit to that, and for me, that limit lands comfortably in the 120-140 character range.
It used to be for me too (132); but not these days (and not here either, if you want to use code tags).
And I say again: do you want your programs to be read?
Winston