eliminating: new Object(<host object>) loophole
allen at wirfs-brock.com
Wed Apr 11 16:58:29 PDT 2012
If we want to get rid of the concept of "host objects" then something that needs to be cleaned up is the specification of implementation dependent behavior of newing the Object constructor with a host object as the argument:
22.214.171.124, step 1.a.ii says: "If the (argument) value is a host object, then actions are taken and a result is returned in an implementation-dependent manner that may depend on the host object."
126.96.36.199, steop 2says: "If O is the result of calling the Object constructor with a host object (188.8.131.52), then Return either O or another value such as the host object originally passed to the constructor. The specific result that is returned is implementation-defined."
Does any one know the purpose of this allowance? Does any known implementation depend upon it?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss