lkml.org 
[lkml]   [2001]   [Nov]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [BUG] Bad #define, nonportable C, missing {}


On 21 Nov 2001, Andreas Schwab wrote:

> Jan Hudec <bulb@ucw.cz> writes:
>
> |> > On Wed, Nov 21, 2001 at 12:40:17PM +0000, vda wrote:
> |> > If you wanna do this type of cleanup, you can take it one step forward;
> |> > remember that the order of evaluation of foo and bar doesn't have to be
> |> > {foo => bar} so it can be {bar => foo} I hope gcc's behaviour doesn't
> |> > change under our feet.
> |> >
> |> > a = foo (i) + bar (j);
> |> >
> |> > .. sprinkle some pointer arithmetic over there for fun ;)
> |>
> |> AFAIK here the order *IS* defined. + operator is evaluated left to right
>
> No. It is undefined which of the operator's arguments is evaluated first,
> unless it is defined otherwise (only for ||, && and comma).

I suspect that real source of problem here is confusion with parsing -
+ operators are _grouped_ left to right. I.e. a+b+c is parsed as (a+b)+c.
Which has nothing to order of evaluation of a, b and c...

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:13    [W:0.057 / U:2.468 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site