Comment by stephencanon
14 years ago
User code built against POSIX should never use the _t suffix; POSIX explicitly puts *_t into the reserved namespace (http://pubs.opengroup.org/onlinepubs/007904975/functions/xsh...), meaning that future revisions may add arbitrary type names of that form, which will break your code if you use the same name and include POSIX headers.
Thbthbthbthbthbththbthtbhtbhthbt! I say to POSIX. This convention is practically universal.
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).
4 replies →