Skip to main content

Java - Order of Operations - Using Two Assignment Operators in a Single Line



What are the order of operations when using two assignment operators in a single line?







public static void main(String[] args){

int i = 0;

int[] a = {3, 6};

a[i] = i = 9; // this line in particular

System.out.println(i + " " + a[0] + " " + a[1]);

}







Edit: Thanks for the posts. I get that = takes values from the right, but when I compile this I get:







9 9 6







I thought it would have been and ArrayOutOfBounds exception, but it is assigning 'a[i]' before it's moving over the 9. Does it just do that for arrays?


Comments

  1. = is parsed as right-associative, but order of evaluation is left-to-right.

    So: The statement is parsed as a[i] = (i = 9). However, the expression i in a[i] is evaluated before the right hand side (i = 9), when i is still 0.

    It's the equivalent of something like:

    int[] #0 = a;
    int #1 = i;
    int #2 = 9;
    i = #2;
    #0[#1] = #2;

    ReplyDelete
  2. As per the specs:


    http://docs.oracle.com/javase/specs/jls/se5.0/html/expressions.html



    15.26 Assignment Operators
    There are 12 assignment operators; all are syntactically right-associative (they group right-to-left). Thus, a=b=c means a=(b=c), which assigns the value of c to b and then assigns the value of b to a.


    So, a[i] = i = 9; is the same as i = 9; a[i] = i;

    ReplyDelete
  3. If I remember correctly, = operator is right-associative; so i will be assigned first, then a[i].

    ReplyDelete
  4. The = operator is right-associative(as others have already said). This can be easily proven with this test:

    int i = 2;
    int j = 3;
    int x = i = j;
    System.out.println(x); // This prints out 3.


    This works with all types, Objects and primitives.

    The way I have heard this referred to is "dual assignment", since, using the example above, you are assigning the value of j to both i and x.

    ReplyDelete
  5. What exactly do you espect to get as an output? There, you are assigning 9 to i and then the value of i to the array (but the array position was already calculed to the 0 position); so, since maybe you are confused about the array position in which the 9 is stored?... First you get a pointer to the a[0] (current value of i) and then, the compiler goes to process the rest of the sentence.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex