On Mon, Sep 8, 2014 at 10:04 AM, Dylan Cali wrote:
> On Sep 8, 2014 9:27 AM, "Eric Blake" wrote:
>> Does this work for all supported versions of gcc? Or do you need to make
>> it conditional on new enough gcc (it's okay if warnings have to be
>> disabled to compile with older gcc, but not okay if
On Sep 8, 2014 9:27 AM, "Eric Blake" wrote:
> Does this work for all supported versions of gcc? Or do you need to make
> it conditional on new enough gcc (it's okay if warnings have to be
> disabled to compile with older gcc, but not okay if the way to disable
> warnings for newer gcc causes compi
On 09/06/2014 07:42 PM, Dylan Cali wrote:
> On Sat, Sep 6, 2014 at 7:30 PM, Paul Eggert wrote:
>> On second thought this doesn't look wise, as the function is not expected to
>> be exported to ordinary clients, only to the test cases. So let's leave the
>> .h file alone, and put a declaration in
