> A stronger case for changing this would be that gcc version > n-1 didn't warn. As discussed elsewhere, some modicum of > stability in warnings is desirable from the user's perspective. > I don't know whether or not this applies in this case.
Well, as I mentioned in the PR, macro writers can wrap the whole thing in a statement expression and avoid the warning. Can't we suggest this and keep (almost) everybody happy?
