WHEN CODING IN SEPPLES
1
Name:
Anonymous
2010-05-08 9:55
I prefer to use printf("ANUS"); over std::COOTER<<"anus";
Is this bad?
2
Name:
Anonymous
2010-05-08 9:58
No. Fuck Sepples iostreams. If you aren't writing directly to file descriptors or handles, use Standard C stdio.
3
Name:
Anonymous
2010-05-08 10:03
How many iterations of this thread are we going to have to sit through?
4
Name:
Anonymous
2010-05-08 10:19
5
Name:
Anonymous
2010-05-08 10:32
Until we blow the stack, because MSVC++ doesn't do TCO.
6
Name:
Anonymous
2010-05-08 10:49
>>5
Actually I've seen MSVC do TCO, but I have no idea under what circumstances it performs it, so it's not nearly as reliable as Scheme's TCO or CL's TCO(which is less reliable, but there are certain general rules you can apply to get a good idea if it'll be performed per implementation).
7
Name:
Anonymous
2010-05-08 11:47
>>2
Fuck you and your 1char = 1byte attitude. We need universal unicode understanding and we need it yesterday
8
Name:
Anonymous
2010-05-08 11:55
>>7
There are base types other than char you know. Even in C!
9
Name:
Anonymous
2010-05-08 12:13
>>7
Fuck you and your 1byte = 8bits attitude. We need a larger CHAR_BIT value and we need it yesterday
10
Name:
Anonymous
2010-05-08 12:24
>>9
Fuck you and your computers = base2 attitude. We need universal Gray code understanding and we need it yesterday
11
Name:
Anonymous
2010-05-08 13:43
>>7
1 char is 1 byte, per C standard. The size of a char or byte is not standard.
12
Name:
Anonymous
2010-05-08 23:21
Stick to c conventions in c, c++ conventions in c++.
Shit starts to get messy when you start mixing them. Suck it up and use std::
13
Name:
Anonymous
2010-05-08 23:27
>>12
Stick to c
conventions in c, c++ conventions in c++ .
14
Name:
Anonymous
2010-05-09 5:55
Suck it up and use std::
or leave the sucking to the french faggots and use c instead of sepples.
16
Name:
Anonymous
2011-02-03 4:14