Hi Martin,

On Sat, 26 Jan 2019, Martin Jambor wrote:
>> What is a "wrong absolute value function"?  That might be good to
>> show by means of an example?  (Also in invoke.texi, which I checked
>> before writing this.)
> I'm not sure how to change the wording, perhaps "...when a used absolute
> value function seems wrong for the type of its argument" ...?

yes, that definitely would have helped me as a user.  (I guessed
it might be that, but seeing it in writing helps.)

On Mon, 28 Jan 2019, Martin Sebor wrote:
>   -Wabsolute-value warns for calls to standard functions that compute
>   the absolute value of an argument when a more appropriate standard
>   function is available.  For example, calling abs(3.14) triggers
>   the warning because the appropriate function to call to compute
>   the absolute value of a double argument is fabs.  The option also
>   triggers warnings when the argument in a call to such a function
>   has an unsigned type.

Lovely.  

(I'd say "This option...", but that's probably a matter of taste.)

Are you going to enhance both invoke.texi and apply a patch to the
release notes (changes.html)?  That would be ideal.

Thanks!

Gerald

Reply via email to