#define TRUE rand()%100
>>107058110retard
I always check the assembly output of my code. Something you have to do for high performance code.
>>107058110>not even parenthesisedtruly devious
#define UNDEFINED 0/0
int GetRandomNumber(){ return 7;}
Madlads, the lot of you.
>>107058110You gotta put your seed in it
>>1070581101. replace legit uses of TRUE with 12. insert a lot of bullshit code referencing TRUE that never gets executed3. watch vibefags get blamed for causing unexplainable downtime
#define 1 0#define 0 1
>>107058110Isn't this wrong? Shouldn't it be %2 since %100 would mean it's true 1% of the time and false otherwise?
>>107064852That's true.
>>107058331>i totally manually check out millions of lines of assemblysure thing buddy
>>107064852you got it backwards 0 is false, everything else is true
>>107064852should be a 1000000 really, you wouldn't want it to be caught too soon
>>107061584int GetRandomNumber() int *ptr; return *ptr;[/code/
int GetRandomNumber() int *ptr; return *ptr;[/code/
>>107065008wait a minute, is this heartbleed?
>>107061584int GetRandomNumber(){ int number = 0; for(int i = 0; i < Math.RandomInt(); i++) { number++; } return number;}
int GetRandomNumber(){ int number = 0; for(int i = 0; i < Math.RandomInt(); i++) { number++; } return number;}
>>107065008Instructions unclear.The guidance system is stick in the ceiling fan.
>>107061584int GetRandomNumber(){ asm("addl %esp, %eax");}
int GetRandomNumber(){ asm("addl %esp, %eax");}
>>107065008This tends to higher value numbers and negatives
>>107066419and we have a WINNER
