Skip to main content

For loop Variations in javascript


In this website there are a list of for loop variations. I can understand the usage of for(var i=0, len=arr.length; i<len ;i++) loop (where arr is an array), since the arr.length isnt calculated every step there is marginal performance gain. However what are the advantages of using the other variants? For instance loops like




  1. for (var i=arr.length; i--;)


  2. for (var i=0, each; each = arr[i]; i++)



Are there any noticeable changes in performance by using different for loop variations? I generally use for(var i=0, len=arr.length; i<len ;i++) even for very big arrays. So I just want to know if there is something I am missing out here.


Source: Tips4allCCNA FINAL EXAM

Comments

  1. It is widely considered that a reversed while loop

    var loop = arr.length;
    while( loop-- ) {
    }


    is the fastest loop-type available in C-like languages (this also applied to ECMAscript for quite a while, but I think all up-to-date engines are pretty even on standard loops today). ( jsperf )

    Your 'variations' are actually no variations, but just different usage of the conditional statement within the for-loop (which, actually makes it a variation..doh!). Like

    1) for (var i=arr.length; i--;)

    Just uses the conditional part from the for-loop to do both, iterating and checking if i has a truthy value. As soon as i becomes 0 the loop will end.

    2) for (var i=0, each; each = arr[i]; i++)

    Here we get the element from each iteration, so we can directly access that within the loop body. This is commonly used when you are tired of always repeating arr[ n ].

    You're doing well in caching the .length property before looping. As you correctly mentioned, it is faster because we don't have to access that property in every iteration. Beyond that, it's also required sometimes in DOM scripting, when dealing with 'live structures' like HTMLCollections.

    ReplyDelete
  2. The point is when you're decrementing the iterator, you're actually comparing it to 0 rather than the length, which is faster since the "<, <=, >, >=" operators require type checks on both left and right sides of the operator to determine what comparison behaviour should be used.

    the fastest loop is: (If you don't care about the order of course)

    var i = arr.length
    while(i--)
    {
    }


    If you do care about the order, the method you're using is fine.

    ReplyDelete
  3. According to jsperf the fastest type of loop in JavaScript is

    var arr = new Array(10);
    var i = 0;
    while (i < arr.length) {
    arr[i];
    i++;
    };


    just ahead of (my default loop)

    var arr = new Array(10);
    for (var i = 0; i < arr.length; ++i) {
    arr[i];
    };


    With this being the slowest :

    var arr = new Array(10);
    arr.forEach(function(x) {
    x;
    });


    at least on Chrome 17 on OSX 10.7.3. So it seems the "default" loop is fine after all !!!

    ReplyDelete
  4. This is a poor use of a for each loop because it will fail on falsy values , breaking the loop.

    for (var i=0, each; each = arr[i]; i++)


    I also wouldn't use this loop ( even tough it may be faster... )

    for (var i=arr.length; i--;)


    It looks confusing and is less readable, you might as well write as reverse while loop then.

    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