The reason why I came up with this is that many code lines are wildly broken at
seemingly random locations.
That makes the code harder to read.
I'll show you what I mean with
good:
if (some.getX().statementA() && some.getY().statementB()) {..
good:
if (some.getX().statementA()
&& some.getY().statementB()) {..
bad:
if (some.getX("bla" +
"blub").statementA(
13) && some.getY
("oh").statementB(
"gosh")) {..
Of course in practice our commands are longer, but similar 'unattractive' to
read ;)
Most times forced by the line length limit.
LieGrue,
strub
> On Friday, 2 September 2016, 16:05, Albert Lee <[email protected]> wrote:
> > I have mixed feeling for this.
>
> I like having a complete statement in one line for visual and logical
> grouping.
> But having multiple statements or constructs in a single long line hinders
> debugging and problem isolation.
>
> +/-0
>
> Albert.
>
>
> On Fri, Sep 2, 2016 at 3:33 AM, Mark Struberg <[email protected]>
> wrote:
>
>> Monitors are big enough these days.
>>
>> 120 chars is really a bit limiting sometimes.
>>
>> wdyt?
>>
>> LieGrue,
>> strub
>>
>
>
>
> --
> Albert Lee.
>
