@cmuratori @TheJare @vgebler "Expression is constant" is useful, it just needs nerfing when it's deliberate.
-
-
Replying to @tom_forsyth
@tom_forsyth@TheJare@vgebler But while(1) is always deliberate, this is my point. Thus that whole series of warnings was illegitimate.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@tom_forsyth@TheJare@vgebler while(var that doesn't happen to change) is very different from while(1).2 replies 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@tom_forsyth@TheJare@vgebler Consider a constant cpp macro whose name is similar to a variable. You might want to catch that.1 reply 0 retweets 0 likes -
Replying to @taradinoc
@taradinoc@tom_forsyth@TheJare@vgebler In no case does that excuse while(1) generating a warning. Yet that was a real VC warning.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@taradinoc@tom_forsyth@TheJare@vgebler I maintain that there is no bug that warning about literal while(1) can catch.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@tom_forsyth@TheJare@vgebler The compiler can't be sure the 1 isn't a macro expansion. for(;;) is an unambiguous alternative.2 replies 0 retweets 0 likes -
Replying to @taradinoc
@taradinoc@tom_forsyth@TheJare@vgebler If your compiler can't tell if the 1 is a literal or an expansion of a macro, you have issues.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@tom_forsyth@TheJare@vgebler No, you just have the traditional preprocessor pipeline.1 reply 0 retweets 0 likes -
Replying to @taradinoc
@taradinoc@tom_forsyth@TheJare@vgebler But if that is your argument, then literally every line of code should produce a warning.1 reply 0 retweets 0 likes
@taradinoc @tom_forsyth @TheJare @vgebler Like, literally every line of code could be an unintended expansion of a macro.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.