Bruno Haible <bruno <at> clisp.org> writes: > > Jim Meyering wrote: > > but since it's just one > > Yes. Currently I see no point in making all the replacement modules compile > in C++ mode. Only those used in a build on a Linux system are needed, > because the purpose of type checking can be achieved on Linux.
I'm trying that idea (using CC=g++ on Linux) on M4 before releasing m4 1.4.8. Is it worth fixing the vasnprintf module? g++ -I. -g -O2 -MT printf-parse.o -MD -MP -MF .deps/printf-parse.Tpo -c -o printf-parse.o printf-parse.c printf-parse.c: In function `int printf_parse(const char*, char_directives*, arguments*)': printf-parse.c:71: error: invalid conversion from `void*' to `char_directive*' printf-parse.c:231: error: invalid conversion from `void*' to `argument*' printf-parse.c:289: error: invalid conversion from `void*' to `argument*' printf-parse.c:501: error: invalid conversion from `void*' to `argument*' printf-parse.c:518: error: invalid conversion from `void*' to `char_directive*' make[2]: *** [printf-parse.o] Error 1 $ uname -a Linux sourceware.org 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:28:02 EDT 2006 i686 i686 i386 GNU/Linux $ gcc --version gcc (GCC) 3.4.6 20060404 (Red Hat 3.4.6-3) ... $ /lib/tls/libc.so.6 --version GNU C Library stable release version 2.3.4, by Roland McGrath et al. ... -- Eric Blake