Yes, I think it matters quite a bit. It would be very easy for someone, even in
their right mind, to unintentionally have an extra comma somewhere in the
middle of a long array literal and not notice it. And the compiler would not
tell them, but instead would insert an empty element at that spot. I would
prefer that the compiler require you to explicitly indicate each element in an
array literal, for example:
var myList:Array = [1, 2, 3, undefined, 4, 5, 6];
Or, absent that, I would prefer that the documentation clearly spell out the
behavior of extra commas in array literals.
________________________________
From: Paul A. <p...@ipauland.com>
To: flexcoders@yahoogroups.com
Sent: Thursday, April 11, 2013 3:00 PM
Subject: Re: [flexcoders] Array literals - odd behavior
Does it really matter? Nobody in their right mind is going to be
populating arrays with multiple commas.
>
