| 1 |
On 06/26/2010 11:12 PM, Ciaran McCreesh wrote: |
| 2 |
> On Sat, 26 Jun 2010 21:57:33 +0200 |
| 3 |
> Enrico Weigelt<weigelt@×××××.de> wrote: |
| 4 |
>>> Uhm. No. Certain compilers will give you warnings for f(g(a), g(b)) |
| 5 |
>>> if you -Wall. |
| 6 |
>> |
| 7 |
>> Warn on what exactly ? |
| 8 |
> |
| 9 |
> That f's arguments are evaluated in an unspecified order. |
| 10 |
> |
| 11 |
>> Which compilers do that ? |
| 12 |
> |
| 13 |
> For all you know, gcc 4.7. |
| 14 |
> |
| 15 |
> New gcc releases regularly issue lots of new warnings for correct code, |
| 16 |
> particularly with -Wall. Other compilers are even worse. |
| 17 |
|
| 18 |
Did it actually occur to anyone that warnings are not errors? You can |
| 19 |
have them for correct code. A warning means you might want to look at |
| 20 |
the code to check whether there's some real error there. It doesn't |
| 21 |
mean the code is broken. |
Archives