Issue 133: Inconsistent errors when using RegExp literals http://code.google.com/p/v8/issues/detail?id=133
New issue report by polarjs: This issue was discovered while investigating ecma_2/RegExp/regress-001.js of the mozilla JS tests. Here's a piece of test code that reduces the issue: ==== BEGIN ================================== var a = /[a-km-z]+/; var b = a("hello"); print("b = " + b); var c = /[a-km-z]+/("hello"); print("c = " + c); ==== END ================================== Running JavaScriptCore, I get: ============================= b = he c = he Running v8 bleeding edge, I get: =============================== test3.js:27: TypeError: Property 'a' of object [object global] is not a function var b = a("hello"); ^ If I swap case 'b' and 'c' in the test, on v8, I get: ===================================================== native runtime.js:177: TypeError: object is not a function throw %MakeTypeError('called_non_callable', [typeof callee]); ^ Why am I getting 2 different errors when the only difference is whether I use the RegExp literal directly or indirectly? Is the second case a v8 internal error? Tested with revision 631 of v8 bleeding edge. Issue attributes: Status: New Owner: ---- -- 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 v8-dev@googlegroups.com http://groups.google.com/group/v8-dev -~----------~----~----~----~------~----~------~--~---