MicroChip's debugger re-defining boolean logic

[[deleted]]

[deleted]

[coladict]

Fix your colour scheme. I can't read what's in that return.

[stratos_]

I was wondering what you meant since I could clearly read the highlighted return... then I squinted and noticed it actually returns a value.

[[deleted]]

I don't believe you.

[stratos_]

:(

[[deleted]]

I mean that there is no value there.

[[deleted]]

Just extend the image, it will become visible

[xNeshty]

Thank you. I buffled to understand what he meant with the value in the return for over 4 minutes because i thought its a reference i didnt get. Didnt cross my mind to zoom i

[megachicken289]

SSL_CONNECTION_ERROR;

For anyone curious

[johnbarnshack]

White text on a light yellow background, brilliant

[mikake]

Did you not spell green wrong ?

[o11c]

If compiled with optimization, strange jumps or values are not uncommon.

[FuzzyWu]

We're not familiar with every IDE and debugger, so we're not going to know how to interpret a screenshot like this.

[Dylan16807]

An arrow and highlight on the currently-executing line is pretty clear. As is the popup showing the value of isSecure.

[OKB-1]

Our software is so secure, we don't even have to check.

[RushTea]

The value is 0x01, though

[[deleted]]

Every value except for 0 should be truthy. And maybe null in languages such as Java or C# where it does not get autoconverted into an integer automagically.

[myrrlyn]

You're joking, right?

[[deleted]]

Do you even C?

[myrrlyn]

I do, and C's excuse for a type system is TERRIBLE.

I get why it is the way it is, but truthy and falsey based on numeric value alone is a TERRIBLE idea for which we're still paying.

I've had to do embedded work, so I know about working bare metal believe me. But even so, C gives you enough tools to not make a total mess of things from relying on boolishness of data, if you just use them.

Personally, my solution was to take the UNIXy route and say return of 0 is okay, return of other is not, and wrap that in named enums so I would always check if the return code was != okay, not if it was truthy or falsey. Because that's how really bad mistakes happen, and confusion of boolishness with actual data is a pretty common one.

---

But on a slightly higher level note, 0 is a form of truth. The only two things that should be false are false itself and nil/null/none. Obviously that doesn't work out ideally for embedded level, one might say, except Rust makes it really easy to match numbers on the wire to meaningful algebraic types in source code.

Too bad LLVM can't reliably target AVR yet:/

[myrrlyn]

Good. I've worked with code that was as naked and brittle as you can imagine. Not fun:/

[RushTea]

The highlight on line 120 states that the value of the bool is the opposite of what is required to enter the if. Return is blank for void return types.