It's frustrating b/c I very much want libc to innovate, but this disdain for reasonable prefixing policy makes it difficult to know what will compile tomorrow...
Saturday, June 5, 2010
I sometimes think a lot of C portability problems are due to lack of namespacing in libc. It's a shame we can't somehow deprecate and move to (eg) ... It would contain familiar functions with a "c_" prefix: c_printf, c_write, etc. This would provide considerably more flexibility to the C implementors and standardizers - for example, I recently ran into a problem with new glibc (patched by a distro) defining "getline" as a macro. (This was in lua's source.. not mine, as it happens)
Subscribe to:
Comments (Atom)