If Statement with QTime

[VJ01]

@JonB

Hi Thank you for the reply honestly instead of two if ststements i just did one with an else and that seemed to work. i was making it more complicated then it should have been haha

if(Final <Final_Night_time && Final > Final_Day_time){
        qDebug() << "DAY TIME";
 }else{
       qDebug() << "NIGHT TIME";
}

Thank you

[Kent-Dorfman]

@VJ01 said in If Statement with QTime:

@JonB

Hi Thank you for the reply honestly instead of two if ststements i just did one with an else and that seemed to work. i was making it more complicated then it should have been haha

if(Final <Final_Night_time && Final > Final_Day_time){
        qDebug() << "DAY TIME";
 }else{
       qDebug() << "NIGHT TIME";
}

Thank you

or in a more sophisticated manner

qdebug() << (((Final < Final_Night_time) && (Final > Final_Day_time)) ? "DAY" : "NIGHT");
// proper parenthesis use and ternary if() clause

[JonB]

@Kent-Dorfman You really like your parentheses, don't you? :)

[jsulm]

@JonB Did you ever see Lisp code? :-)

[JonB]

@jsulm They are compulsory there, I (mostly) only put in the mandatory ones in C++ and omit the rest.

[Kent-Dorfman]

You parenthesis free folks wouldn't like a MISRA/AUTOSAR audit. LOL!

https://www.autosar.org/fileadmin/standards/adaptive/18-03/AUTOSAR_RS_CPP14Guidelines.pdf

If/else clauses really stress my OCD when they represent binary code paths...and worse when there are more than three of them...It's like Dude! use a switch/case or a map of function pointers. PLLLEEEEAAASSSEEE!!!

[JonB]

@Kent-Dorfman
That's nearly 500 pages of rules to observer/remember! Very worthy, I can see it being advisable in critical stuff, thankfully I have not had to adhere. TBH if you need to adhere to this many rules it does make me wonder whether you need a different language which enforces more of this stuff?

[Kent-Dorfman]

@JonB Generally very few institutions take it in its entirety, but at the beginning of a project decide what rules to enforce, which to ignore, and a policy for warning suppression (be prepared to defend why you ignored rule XXX in code review)

It's primary domain has been in the automobile automation industry, which as you can guess, needs to be pretty safety critical...but it's finding its way into other industries as well. In space systems we use it as a base, obviously.

Any virtually no one tries to adhere without a code scanner program to check for violations.

[jsulm]

@JonB said in If Statement with QTime:

it does make me wonder whether you need a different language which enforces more of this stuff

Indeed. Instead of reading these 500 pages and try to remember later all these restrictions/rules it would be better to use a programming language which reduces the need to remember such rules. Do you remember the "Port Qt to Rust" thread? :-)

[JonB]

@jsulm said in If Statement with QTime:

Do you remember the "Port Qt to Rust" thread? :-)

That was what I had in mind.... Maybe that would enforce half the C++ rules, without needing to impose an equal number of new ones for Rust?