Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

13
  • 7
    There is something wrong with it; ` != NULL` and its kin in a C conditional are natter, just there to placate developers who aren't comfortable with the concept of a value being true or false (or vice-versa). Commented Oct 30, 2016 at 15:33
  • 1
    @jcast No, it's more explicit to include != NULL. Commented Oct 30, 2016 at 21:35
  • 1
    No, it's more explicit to say (x != NULL) != 0. After all, that's what C is really checking, right? Commented Oct 30, 2016 at 21:38
  • @jcast No, it isn't. Checking whether something is unequal to false is not how you write conditionals in any language. Commented Oct 30, 2016 at 21:41
  • "Checking whether something is unequal to false is not how you write conditionals in any language." Exactly. Commented Oct 30, 2016 at 21:43