On 10/25/2016 10:21 AM, Felipe Franciosi wrote:
>
>> On 12 Oct 2016, at 18:20, Felipe Franciosi wrote:
>>
>>
>>> On 21 Sep 2016, at 19:15, Eric Blake wrote:
>>>
>>> On 09/21/2016 10:27 AM, Felipe Franciosi wrote:
On GCC versions 3.4 and newer, simply using (void) in front of a
function
> On 12 Oct 2016, at 18:20, Felipe Franciosi wrote:
>
>
>> On 21 Sep 2016, at 19:15, Eric Blake wrote:
>>
>> On 09/21/2016 10:27 AM, Felipe Franciosi wrote:
>>> On GCC versions 3.4 and newer, simply using (void) in front of a
>>> function that has been declared with WUR will no longer suppres
> On 21 Sep 2016, at 19:15, Eric Blake wrote:
>
> On 09/21/2016 10:27 AM, Felipe Franciosi wrote:
>> On GCC versions 3.4 and newer, simply using (void) in front of a
>> function that has been declared with WUR will no longer suppress a
>> compilation warning. This commit brings the ignore_value(
On 09/21/2016 10:27 AM, Felipe Franciosi wrote:
> On GCC versions 3.4 and newer, simply using (void) in front of a
> function that has been declared with WUR will no longer suppress a
> compilation warning. This commit brings the ignore_value() macro from
> GNULIB's ignore_value.h, licensed under t
On GCC versions 3.4 and newer, simply using (void) in front of a
function that has been declared with WUR will no longer suppress a
compilation warning. This commit brings the ignore_value() macro from
GNULIB's ignore_value.h, licensed under the terms of LGPLv2+.
See the link below for the origina