Problem (?) with Nashorn management of Error prototype

[A. Sundararajan]

This is w.r.t this email:

http://mail.openjdk.java.net/pipermail/nashorn-dev/2014-October/003582.html

Hi,

did you manage a simpler test case? Internal runtime errors like 
TypeError on function-call-on-undefined etc.  are created using 
Global.newTypeError, newURIError etc. - which actually create objects of 
specific impl. classes like NativeTypeError, NativeURIError and so on. 
This is as per the spec AFAIK - i.e., runtime can use "original" 
definitions of these constructors rather than the value fetched from 
current global's properties of same name ("Error", "TypeError" 
properties of global object). I don't recall any other place where there 
is specific prototype/constructor assumed/hard coded in nashorn.

Thanks,
-Sundar