Albert Chin wrote:
> > I'm worried that more differences between the C and C++ compilers are
> > found. It may be not only the location of , but also
> > HAVE_DECL_STRRCHR, the presence of an uint32_t type, etc.
>
> Possibly. lftp-3.5.11, an ftp client which is more a mix of C/C++,
> exposes more
> On Sat, 1 Sep 2007 22:15:58 +0200, Bruno Haible wrote:
> > On 11.x/PA,
> > the HP C++ compiler does not support #include_next. So, we get
> > #include "///usr/include/string.h". This fails to include the
> > C++-specific and thus some functions like strchr() don't
> > get defined, leading to com
Hello Albert,
> On 11.x/PA,
> the HP C++ compiler does not support #include_next. So, we get
> #include "///usr/include/string.h". This fails to include the
> C++-specific and thus some functions like strchr() don't
> get defined, leading to compile failures. When you #include
> in a C++ program
We recently built poppler-0.5.4, a C++ library, and had to bring in
gnulib for snprintf() on Tru64 UNIX. Because of this, lib/string_.h ->
lib/string.h which the HP C++ compiler has a problem with. On 11.x/PA,
the HP C++ compiler does not support #include_next. So, we get
#include "///usr/include/s
