<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Feb 8, 2012, at 10:17 AM, David Blaikie wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">I'm also reminded of Chandler's talk at GoingNative last week when he<br>mentioned that the -Wparentheses warning didn't used to have the<br>inverse (checking that you /don't/ use extra () when you're just doing<br>an equality not an assignment) & this was added. But I know it's not a<br>perfect analogy because the extra () were already<br>deliberately/habitually for -Wparentheses in the first place. Good<br>that we could have negative & positive warnings on at the same time by<br>default in that case.</span></blockquote></div><br><div>A fair point. I think it's worth pointing out that a fair number of people disliked this change, so much that they requested that we could put the inverse case under a different warning flag so they could turn it off.</div><div><br></div><div>I'm leaning that this should be under -Wall after all, but it would be great to hear other opinions here.</div></body></html>