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
