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. binuti
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?
Fixes
warning: request for implicit conversion from ‘void *’ to ‘struct
_obstack_chunk *’ not permitted in C++ [-Wc++-compat]
I moved the assignment to h->chunk to fix an overlong line, then
decided it would be better after the alloc failure check just to do
things the same way as in _obstack_new
