@staatsgeheim @canadianbryan I don't think you understand what "the wrong thing" means.
-
-
Replying to @staatsgeheim
@staatsgeheim@canadianbryan int main() { char buf[snprintf(0,0,"%d",rand())+1]; srand(1); sprintf(buf,"%d",rand()); }1 reply 0 retweets 0 likes -
Replying to @RichFelker
@staatsgeheim@canadianbryan This is a strictly conforming C program (mod#include not fitting in tweet) that breaks dangerously on OpenBSD.1 reply 0 retweets 0 likes -
Replying to @RichFelker
@staatsgeheim@canadianbryan Similar examples can be made with real-world simulations done in two passes, but don't fit in 140 chars.1 reply 0 retweets 0 likes -
Replying to @RichFelker
@staatsgeheim@canadianbryan In particular 2-pass encoding with mplayer is broken with -vf noise; each pass sees different frames.2 replies 0 retweets 0 likes -
Replying to @staatsgeheim
@staatsgeheim@canadianbryan They broke valid correct programs for a false sense of fixing hopelessly broken ones.2 replies 0 retweets 0 likes -
Replying to @RichFelker
@staatsgeheim@canadianbryan Any sw using rand() where csprng is needed has MUCH BIGGER issues and simply cannot be used without full audit.2 replies 0 retweets 0 likes -
Replying to @RichFelker
@staatsgeheim@canadianbryan In any case your pkg manager can just enforce not allowing programs except whitelisted ones to use rand().1 reply 0 retweets 0 likes
@staatsgeheim @canadianbryan Changing a standard function to do something contrary to its specification is simply not an acceptable solution
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.