Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
On 06/26/2010 11:12 PM, Ciaran McCreesh wrote:
> On Sat, 26 Jun 2010 21:57:33 +0200
> Enrico Weigelt<weigelt@...> wrote:
>>> Uhm. No. Certain compilers will give you warnings for f(g(a), g(b))
>>> if you -Wall.
>>
>> Warn on what exactly ?
>
> That f's arguments are evaluated in an unspecified order.
>
>> Which compilers do that ?
>
> For all you know, gcc 4.7.
>
> New gcc releases regularly issue lots of new warnings for correct code,
> particularly with -Wall. Other compilers are even worse.
Did it actually occur to anyone that warnings are not errors? You can
have them for correct code. A warning means you might want to look at
the code to check whether there's some real error there. It doesn't
mean the code is broken.
|
|
