Bruno Haible <br...@clisp.org> writes: > Should the 'regex' module (and possibly other modules which require C > syntax) depend on the 'no-c++' module? We can open a poll on it.
I don't understand the rationale for the no-c++ module, let alone making any other modules depend on it. What is the issue with compiling C code with a C compiler and C++ code with a C++ compiler? That seems to be me the proper solution. Compiling C code with a C++ compiler seems like a good recipe for problems, and I don't think it is something gnulib should force on users unless there is a compelling use-case. Having the support optional in gnulib is fine by me, i.e. each maintainer that wants the behaviour would add the no-c++ module and adapt their build infrastructure as appropriate. Without understanding, my preference is to not make other modules depend on no-c++. /Simon
