Le 20/03/2013 19:08, Jeff Walden a écrit :
I don't see what can reasonably be done about it, without effectively mandating
attempting NaN-substitution whenever the value to set might be NaN.
+1. I think Safari needs to be fixed.
Stuffing info in NaNs sounds superfluous. JS has objects, arrays, Typed
Arrays, strings. Largely enough legitimate mechanisms to represent
informations without having to add a hacky one. That would be sending a
wrong signal to developers in my opinion.
David
_______________________________________________
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
