associativity

Ahh, don't you just love a good ternary abuse? :) Consider the following expression: true ? true : true ? false : false For those of you who are now utterly perplexed, I can tell you that this evaluates to true . In other words, it's equivalent to this: true ? true : (true ? false : false) But is this reliable? Can I be certain that under some circumstances it won't come to this: (true ? true : true) ? false : false Some might say - well, just add parenthesis then or don't use it altogether - after all, it's a well known fact that ternary operators are evil! Sure they are, but there are some

I understand that the assignment operator is right associative. So for example x = y = z = 2 is equivalent to (x = (y = (z = 2))) That being the case, I tried the following: foo.x = foo = {a:1} I expected that the object foo would be created with value {a:1} and then the property x will be created on foo which will just be a reference to the foo object. (This is actually what happens if I was to separate the multiple assignment statement into two separate statements foo = {a:1};foo.x = foo; ) The outcome was actually: ReferenceError: foo is not defined(…) So then I tried the following: var foo

The C++ operator precedence table from http://en.cppreference.com/w/cpp/language/operator_precedence (I know it's not normative, but the standard doesn't talk about precedence or associativity) marks unary operators as right/left associative. From a discussion on a different question, I'm left with doubts. Does it make sense for unary operators to be associative? It's just an artefact of the way that the associativity is derived from the grammar. The reason that addition is left-associative is that one of the productions for additive-expression is additive-expression + multiplicative

Introduction In every textbook on C/C++, you'll find an operator precedence and associativity table such as the following: http://en.cppreference.com/w/cpp/language/operator_precedence One of the questions on StackOverflow asked something like this: What order do the following functions execute: f1() * f2() + f3(); f1() + f2() * f3(); Referring to the previous chart I confidently replied that functions have left-to-right associativity so in the previous statements the are evaluated like this in both cases: f1() -> f2() -> f3() After the functions are evaluated you finish the evaluation like

What is associativity (for an operator) and why is it important? Updated: operator associativity For operators, associativity means that when the same operator appears in a row, then which operator occurence we apply first. In the following, let Q be the operator a Q b Q c If Q is left associative, then it evaluates as (a Q b) Q c And if it is right associative, then it evaluates as a Q (b Q c) It's important, since it changes the meaning of an expression. Consider the division operator with integer arithmetic, which is left associative 4 / 2 / 3 <=> (4 / 2) / 3 <=> 2 / 3 = 0 If it were right

We get into unnecessary coding arguments at my work all-the-time. Today I asked if conditional AND (&&) or OR (||) had higher precedence. One of my coworkers insisted that they had the same precedence, I had doubts, so I looked it up. According to MSDN AND (&&) has higher precedence than OR (||). But, can you prove it to a skeptical coworker? http://msdn.microsoft.com/en-us/library/aa691323(VS.71).aspx bool result = false || true && false; // --> false // is the same result as bool result = (false || true) && false; // --> false // even though I know that the first statement is evaluated as