Comment #3 on issue 133 by [email protected]: Inconsistent errors when using
RegExp literals
http://code.google.com/p/v8/issues/detail?id=133
This is unrelated to RegExps, and happens whenever we attempt to call a
non-function
expression that doesn't have a name (a non-Reference value):
> var d = "xyz"("arg");
native runtime.js:177: TypeError: string is not a function
throw %MakeTypeError('called_non_callable', [typeof callee]);
^
It does indeed expose internal details in the exception display. If we do
report a
position for the error, it would be more user-friendly to report the point
in the
user code where the error occoured.
This does not affect V8 in Chromium. The message is printed by the shell/d8
wrapper
code, which requests verbose exceptions, and is not part of the exception
fields
accessible from JavaScript.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
-~----------~----~----~----~------~----~------~--~---
