Re: make safe_read usable in a mixed C/C++ build

2007-01-04 Thread Lorenzo Bettini
Bruno Haible wrote: > Eric Blake asked: >> Is it also necessary to wrap safe-read.c with extern "C", for use when >> using g++ as a type-safe variant of a C compiler, to match the header? > > Normally not. The 'extern "C"' is only needed in mixed C/C++ builds. > >> And should you be symmetric wit

Re: make safe_read usable in a mixed C/C++ build

2007-01-02 Thread Bruno Haible
Eric Blake asked: > Is it also necessary to wrap safe-read.c with extern "C", for use when > using g++ as a type-safe variant of a C compiler, to match the header? Normally not. The 'extern "C"' is only needed in mixed C/C++ builds. > And should you be symmetric with safe-write.h? I deal with th

Re: make safe_read usable in a mixed C/C++ build

2006-12-23 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bruno Haible on 12/23/2006 8:41 AM: > Hi Jim, > > For some complicated reasons (too long to explain here), gettext needs to > use safe-read.h with a C++ compiler on mingw and cygwin. Is this patch ok > with you? Is it also necessary to w

Re: make safe_read usable in a mixed C/C++ build

2006-12-23 Thread Jim Meyering
Bruno Haible <[EMAIL PROTECTED]> wrote: > For some complicated reasons (too long to explain here), gettext needs to > use safe-read.h with a C++ compiler on mingw and cygwin. Is this patch ok > with you? > > 2006-12-23 Bruno Haible <[EMAIL PROTECTED]> > > * lib/safe-read.h [C++]: Wrap decla

make safe_read usable in a mixed C/C++ build

2006-12-23 Thread Bruno Haible
Hi Jim, For some complicated reasons (too long to explain here), gettext needs to use safe-read.h with a C++ compiler on mingw and cygwin. Is this patch ok with you? 2006-12-23 Bruno Haible <[EMAIL PROTECTED]> * lib/safe-read.h [C++]: Wrap declarations in extern "C". *** gnulib-20061