Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: Arguments's toString changed due to ES5?
0 views
Skip to first unread message
Cameron McCormack
Dec 16, 2009, 5:37:19 PM12/16/09
to
On 17/12/2009 3:14 AM, Marc Guillemot wrote:
> due to changes in Rhino Head, toString() on an Arguments object now
> returns "[object Arguments]" whereas it was correctly returning "[object
> Object]" in earlier Rhino versions.
>
> Is this changed due to ES5 support? I couldn't find anything in the spec
> motivating it.
> due to changes in Rhino Head, toString() on an Arguments object now
> returns "[object Arguments]" whereas it was correctly returning "[object
> Object]" in earlier Rhino versions.
>
> Is this changed due to ES5 support? I couldn't find anything in the spec
> motivating it.
In the CreateArgumentsObject abstract operation in section 10.6, it
states that the [[Class]] of the object is "Arguments" and that its
[[Prototype]] is the Object prototype object, which means that
Object.protoype.toString will return "[object Arguments]".
Marc Guillemot
Dec 17, 2009, 4:43:51 AM12/17/09
to
Thanks, I've missed it.
Any plans to make ES5 features working only when the right JavaScript
version is set on the Context?
Cheers,
Marc.
Cameron McCormack a �crit :
0 new messages