← Back to context Comment by tptacek 14 years ago Thbthbthbthbthbththbthtbhtbhthbt! I say to POSIX. This convention is practically universal. 6 comments tptacek Reply stephencanon 14 years ago Just so long as I don't see you filing any bug reports when POSIX changes a header and your code stops compiling. =) spc476 14 years ago That's why I use *__t (two underscores). obiterdictum 14 years ago That's not ideal either.http://www.doc.ic.ac.uk/lab/cplus/c++.rules/chap5.html"The use of two underscores (`__') in identifiers is reserved for the compiler's internal use according to the ANSI-C standard." 3 replies →
stephencanon 14 years ago Just so long as I don't see you filing any bug reports when POSIX changes a header and your code stops compiling. =) spc476 14 years ago That's why I use *__t (two underscores). obiterdictum 14 years ago That's not ideal either.http://www.doc.ic.ac.uk/lab/cplus/c++.rules/chap5.html"The use of two underscores (`__') in identifiers is reserved for the compiler's internal use according to the ANSI-C standard." 3 replies →
spc476 14 years ago That's why I use *__t (two underscores). obiterdictum 14 years ago That's not ideal either.http://www.doc.ic.ac.uk/lab/cplus/c++.rules/chap5.html"The use of two underscores (`__') in identifiers is reserved for the compiler's internal use according to the ANSI-C standard." 3 replies →
obiterdictum 14 years ago That's not ideal either.http://www.doc.ic.ac.uk/lab/cplus/c++.rules/chap5.html"The use of two underscores (`__') in identifiers is reserved for the compiler's internal use according to the ANSI-C standard." 3 replies →
Just so long as I don't see you filing any bug reports when POSIX changes a header and your code stops compiling. =)
That's why I use *__t (two underscores).
That's not ideal either.
http://www.doc.ic.ac.uk/lab/cplus/c++.rules/chap5.html
"The use of two underscores (`__') in identifiers is reserved for the compiler's internal use according to the ANSI-C standard."
3 replies →