4 ms·

I hope it doesn't warn for things like if(0 != (i = getValue()))

• chris_wot 11y ago
  I hope it does!
  • PeCaN 11y ago
    Why would that be a warning? It's quite clear what that code is doing and is a reasonably common C idiom.
    • chris_wot 11y ago
      Yeah, fair enough. It's not bad - I had to think about my objection to it and it's probably largely unfounded.
    • malka 11y ago
      the problem being refered to here is : > if (i = 0) instead of > if (i == 0)
• tspiteri 11y ago
  It doesn't since the assignment is in brackets. You can also write if ((i = getValue()))
  • deleted 11y ago
    [deleted]
• sigjuice 11y ago
  Why not be absolutely sure? if (0 != (0 != (i = getValue())))
  • ifdefdebug 11y ago
    I am aware of the redundancy, this was about the new warnings. If you can't do if(i = getValue()) without warning, I was wondering if assignments as a part of a larger expression would pass.