[quakenet] <day> Edible: not shady at all. i think my favorite is "bool a = 2; if(a == 1) printf("a==1"). bool feels like a shitty define trick with a few extra traps
08:19
[quakenet] <day> i get that within the confines of c it probably is the best you can do. but why even do it in the first place. if someone wanted to use true/false they could simply define it themselves.
well libs are there to give safe implementations of concepts. Can't imagine libc be like "eh we could write strlen but it's really easy, we'll leave that as an exercice"
[quakenet] <day> It made me realize how little the compiler cares, or rather how weakly typed c is. I never really tried to abuse the type system before.
You figure that the day you make a class with a constructor C(bool). Almost any other type can be converted to C through bool conversion, and then it's hell when you fail something
[quakenet] <day> good thing it wasnt an unsigned int :p
10:55
[quakenet] <day> c makes you declare every variable with a specific type and then it goes like "nah that was just to hazzle you, I dont care about types lol"
10:56
[quakenet] <Dune> thanks to c++11 you can give up on code readability and put auto everywhere
10:57
[quakenet] <Dune> who is paid to read code anyway? people are paid to write
10:57
[quakenet] <day> pff. c has auto too. its called "double"
