False. You can have anything you want in an Array, since it's just an object.
var arr = [];
arr["hello"] = 57;
arr.world = function() {};
arr[999.99] = "flibble!";
arr[54] = 9;
// arr.length now equals 55
May or may not be a good coding style, but that's a separate matter.[] and {} seem to be identical, except that [] one auto-increments a key-as-string in its initialization syntax.
Yes, an _ before the string would fix that particular interactive session, but it's not going to work in general.
In general, most don't use the same String value for a key/index to store different values. Just my opinion on that one, though.
Oh, and: you can use Firebug to effectively see the difference between the two.
>>> x = ["1"];
["1"]
>>> x = {"1": "1"};
Object 1=1Sorry, didn't mean to be a dick. :) This particular wart apparently got my nerd rage going.
> In general, most don't use the same String value for a key/index to store different values
Agreed, it'd generally be pretty sketchy. My current puttering around project is a "Python-in-JS" in the vein of http://objective-j.org/ which is where the desire for a "map" rather than an "object" comes from.
However, for an Object (if they used {} instead of []), the property gets converted using String() before being assigned, so you cannot have duplicate values with the same String value. This actually makes sense when you consider that JavaScript isn't a hard typed language and you often don't need to type cast (which comes in handy more often than it fails a programmer).
My opinion: this guy is complaining just to complain, he could throw a _ before that 1 String and it solves his type problem completely.