On May 13, 2010, at 10:21 PM, Alex Russell wrote: > On May 13, 2010, at 5:15 PM, Vladimir Vukicevic wrote: > >> This is difficult to do, given the goals of typed arrays -- they wouldn't >> behave like normal Arrays in most meaningful ways. > > Sounds like a bug to be fixed ;-) > >> At the core, an ArrayBuffer is of fixed size, and it doesn't make sense to >> index an ArrayBuffer directly (because there's no indication of what format >> the data should be accessed in). Making the array view types instances of >> Array might work, but again given that they're fixed length, there's a >> significant difference there. > > > That the length property of a particular array subclass leaves the > constructor non-configurable and read-only isn't much of a trick in ES5. That > said, why *doesn't* TypedArray spec a mutable variant? Surely it'd be useful.
The data is mutable, the length is not -- this is more in line with arrays in other languages, but more importantly the whole point of the typed array spec was to provide a compact typed storage mechanism. Allowing the length to be changed runs counter to this as it effectively puts us back in the position of supporting sparse arrays. --Oliver > > Regards > > -- > Alex Russell > [email protected] > [email protected] BE03 E88D EABB 2116 CC49 8259 CF78 E242 59C3 9723 > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
