Are there any style guidelines or conventions for formatting complex logic?

Question

I was working on a project that included complex logic logic. This complexity made the code very efficient, but unfortunately it is difficult to read.

So, we laid the logic, as shown below, which simplified the viewing of groups within compound statements, and also allowed us to add comments to parts of the logic.

(This code is not real code from the project, the real logic was more complex)

if  (
        //comments here!            
        angle.angle < kQuiteLow 

     && (
            previousAngle.angle > kQuiteHigh
         || previousAngle.time == kUnknownTime
        )

        //comments in here too!         
     && pairedAngle.angle < kQuiteLow 

     && (
            //and here
            previousPairedAngle.angle > kQuiteHigh
         || previousPairedAngle.time == kUnknownTime
        )
    )

Have you ever seen this elsewhere?

Are there any conventions or guidelines for style guides on how to lay out very complex logic?

Answer 1

, .

if( ValidAngle(angle, previousAngle) && ValidAngle(pairedAngle, previousPairedAngle) )

ValidAngle( angle, prevAngle){
    return angle.angle < kQuiteLow && (previousAngle.angle > kQuiteHigh || previousAngle.time == kUnknownTime)
}

Answer 2

. , . , , .

if (anglesAreOk(...))
{
}

public bool analyseAngles() {
    return angleOk(...) && previousAngleOk(...) && pairedAngleOk(...)
}

...

Answer 3

samuelcarrijo pb, .

, .

Answer 4

, , .

if(x && y || !b) { }

if(customerIsRepeatCustomerFromIdaho(x,y,b)){ }

.

[Test]
public void CustomersFromIdahoGetDiscountsOnAlternatingTuesdays()
{
  isRepeat=true;isFromIdaho=false;isTuesday=true;
  Assert.AreEqual(Customer.CalclateDiscount(isRepeat,isFromIdaho,isTuesday),.10)
}

Answer 5

?

.

if ( angle.isQuiteLow() && previousAngle.isQuiteHigh() && previousAngle.isUnknownTime() )