[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Silence obstack.c -Wc++compat warning
|
From: |
Alan Modra |
|
Subject: |
Re: Silence obstack.c -Wc++compat warning |
|
Date: |
Tue, 10 Nov 2015 09:20:58 +1030 |
|
User-agent: |
Mutt/1.5.23 (2014-03-12) |
On Mon, Nov 09, 2015 at 07:40:06AM -0800, Paul Eggert wrote:
> Generally we don't worry about C++ compatibility when maintaining C code, as
> it complicates the code and there's typically not enough benefit to justify
> it. Is there some reason obstack.c should be an exception?
Not really. binutils, gdb, and gcc are all built with -Wc++compat
nowadays so I have applied this patch to the obstack source in
libiberty, to pacify the C++ fanatics.
I'm not concerned that the sources diverge, given the low frequency of
updates to libiberty's obstack code in the past.
--
Alan Modra
Australia Development Lab, IBM