ITT we make /g/ approved insults. I'll start.
If you were a method in C, you would be fgets.
Because it sounds like faggot. I told this one to be CS professor. He looked a bit weird about it, probably because he got burned. Anybody else wanna share some?
Off yourself.
>>54539091
Off yourself
>>54539099
If you were a method in C, you would be fgets.
>>54539091
Fucking fight me you scarab
>>54539107
You're so bad you're not worth debugging, we'll need to start from scratch.
These are pretty good.
>>54539091
Your mother is so fat, the recursive function computing her mass causes a stack overflow.
>>54539445
I like this one a lot.
>>54539091/* This causes a segmentation fault */
sizeof(yourMom);
>>54539091
You're as hot as a reference gtx 480!
>>54539091
Off yourself.
Also, gets wouldn't been a better insult.
>>54539721
You sure are fucking retarded.
You don't know what a segfault is, do you?
No where insizeof(yourMom);is a memory access taking place, therefore it as impossible for any kind of memory fault to occur. infact that entire expression is evaluated at compile time.
Kill yourself.
>>54541426
>No where in sizeof(yourMom); is a memory access taking place,
False.
>>54539091
You're a flow control construct made with gotos.
>>54541503
Got anything to back that claim up with?sizeof(yourMum);by it's self (as it was in his post) is just simply a literal.
and he's not assigning it to any variable, so it's just simply discarded in a register somewhere and overwritten.
And registers can't cause memory faults.
>>54541647
In fact, the compiler probably optimized it out completely.
>>54539108
underrated post
op.Dispose();
>>54539445
> not integer overflow
> not using tail recursion
