On 05/05/11 10:48, Bruno Haible wrote: > But with gnulib, we have three territories: the C implementation, gnulib, > and the application. From the point of the C implementation, gnulib is > application code. From the point of the application, gnulib is part of the > C implementation. So we have to use a careful pragmatic choice in order > not to conflict with one or the other.
Yes, and I'm not saying we should change things, but we need to be clear: gnulib infringes both on the implementation space (via _GL_...) and on the application space (via _gl_...). We could easily modify gnulib to infringe on just one space, or just on the other; but we've chosen to put a plague on both houses. :-)
