On 03/20/2011 01:58 PM, Bruno Haible wrote: > the first action should be to ping the glibc maintainers about it. > If they close it as rejected / invalid / won't fix, then IMO we can consider > to do something in gnulib about it.
That's already been done. The bug hasn't been closed, but indications are that it won't be fixed. On 03/20/2011 01:58 PM, Bruno Haible wrote: > You can test C++ compatibility by doing > $ ./gnulib-tool --test --with-tests --with-c++-tests stdio I'll look into this, but I'm afraid this may still presume more C++ competence than I have. I'll look into fixing the other problems you mentioned (and thanks for reviewing it). For C++ another option is to make the patch conditional on the compiler not being C++; that way, C++ compilers, for good or for ill, won't be affected by the patch.
