This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Problems with gcc + exceptions + -pedantic + libiberty.h
- From: John Levon <levon at movementarian dot org>
- To: gcc-patches at gcc dot gnu dot org, binutils at sources dot redhat dot com
- Cc: dj at delorie dot com
- Date: Tue, 8 Jan 2002 18:26:57 +0000
- Subject: Re: Problems with gcc + exceptions + -pedantic + libiberty.h
- References: <20020107235319.GA93680@compsoc.man.ac.uk> <200201080007.g08074U02537@envy.delorie.com> <20020108001602.GC21859@bubble.sa.bigpond.net.au> <200201080028.g080SPb02685@envy.delorie.com> <20020108041738.GG21859@bubble.sa.bigpond.net.au> <200201080428.g084Sl905133@envy.delorie.com>
On Mon, Jan 07, 2002 at 11:28:47PM -0500, DJ Delorie wrote:
> 2. C++ source shouldn't ever see the () decl, me thinks. It's inside
> an extern "C" but I have this nagging feeling I've seen C++ sources
> complain if they don't also see the real prototype.
How about :
1) teaching GNU libc string.h to set HAVE_DECL_BASENAME
and
2) including string.h (+ stdio.h) in libiberty.h
That way the headers will "just work" in C++ without my application having to
worry about setting HAVE_DECL_BASENAME myself.
I'm not exactly fond of platform-specific hacks myself, but it would perhaps
reduce the complexity of the necessary autoconfigurey in my project to see if
c++ -pedantic is going to work in this case or not
regards
john
--
"I went to set up a Yahoo ID for my dog. (Don't ask, but the DOG'S email was cluttering my inbox)."
- Ruthless Advisorette