• Create Account

### #Actualslicer4ever

Posted 18 April 2013 - 07:51 AM

On the other hand, you've got this:

if ((a || b) && (c || d) && (e || f)) {
DoSomething ();
DoSomethingElse ();
}


Versus this:

if ((a || b) && (c || d) && (e || f))
DoSomething ();
DoSomethingElse ();
}


The second one here is wrong (and won't even compile, but that's by the by for now) but the wrongness doesn't jump out at you like it should.

I've programmed in that style for a long time, it jumped out to me immediately, without any need for an editor to format it and before reading your last sentence pointing it out.  I understand the point you are trying to make, but having coded like that for a long time, such mistakes very rarity occur, and when they do, i'm not digging through a ton of code to find it, it's generally pretty quick and easy to discover.

### #2slicer4ever

Posted 18 April 2013 - 07:50 AM

On the other hand, you've got this:

if ((a || b) && (c || d) && (e || f)) {
DoSomething ();
DoSomethingElse ();
}


Versus this:

if ((a || b) && (c || d) && (e || f))
DoSomething ();
DoSomethingElse ();
}


The second one here is wrong (and won't even compile, but that's by the by for now) but the wrongness doesn't jump out at you like it should.

I've programmed in that style for a long time, it jumped out to me immediately, without any need for an editor to format it and before reading your last sentence pointing it out.

### #1slicer4ever

Posted 18 April 2013 - 07:47 AM

On the other hand, you've got this:

if ((a || b) && (c || d) && (e || f)) {
DoSomething ();
DoSomethingElse ();
}


Versus this:

if ((a || b) && (c || d) && (e || f))
DoSomething ();
DoSomethingElse ();
}


The second one here is wrong (and won't even compile, but that's by the by for now) but the wrongness doesn't jump out at you like it should.

I've programmed in that style for a long time, it jumped out to me immediately, without any need for an editor to format it or point it out to me.

PARTNERS