Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!news-1.dfn.de!news.dfn.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Mel Smith" Newsgroups: comp.lang.javascript Subject: Re: 'pushing' vs direct array assignment ? Date: Mon, 3 Jun 2013 20:38:37 -0600 Lines: 20 Message-ID: References: <7dc473f5-c0e8-415b-92e1-f6201220fe9d@j8g2000yqa.googlegroups.com> X-Trace: individual.net aEkciRB2mrKT+NARkjwYjAVnXJvjtoA6m9xxiE0hENFyTTXUNW Cancel-Lock: sha1:1xPCA4gAMzT/9jh4sinLHrhOtwU= X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-RFC2646: Format=Flowed; Response Xref: csiph.com comp.lang.javascript:20138 I said: "> I'll see if I have the length of the array available when I start my > 'pushing' or 'insertion' or whatever -- my largest array is approx 1434 > elements, each containing a property with 2 properties. Typo: I actually have to build *two* arrays each having a maximum sixe of approx 1434 elements. Each of the array elements has an object with two properties. Instead of building the arrays during the 'onload' stage, I move the array builder to an 'onclick' function. -Mel