Just to clarify this
new Date() normally produces a perfectly ok Date object representing the current date and time. Does your change to ES5 mean that JSON.stringify([ <any date object> ]) will produce [null]? And if not, why should it refuse to stringify the current date and time in this manner when other dates and times give meaningful results?
] På vegne af Douglas Crockford
Sendt: 18. juni 2009 18:43
Emne: [json] new Date(NaN)
We will be correcting the ES5 standard to emit null in this case.
The 2009-06-18 edition of json2.js contains the change.
Thanks to Joel Finch for the heads up.
[Non-text portions of this message have been removed]