Closed Bug 248772 Opened 20 years ago Closed 12 years ago

JSOPTION_STRICT won't allow eval through JS_CallFunction* or JS_Evaluate*

Categories

(Core :: JavaScript Engine, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: ggadwa, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us) AppleWebKit/125.2 (KHTML, like Gecko) Safari/125.8
Build Identifier: 

Get rid of the strict warning when the caller is using the JS_Call* or JS_Evaluate* APIs to call 'eval'.

Reproducible: Always
Steps to Reproduce:
1. Setup a JS runtime with:
JS_SetOptions(js.cx,JS_GetOptions(js.cx)|JSOPTION_STRICT|JSOPTION_VAROBJFIX|JSOPTION_WERROR);
2. call 'eval' through JS_CallFunctionName

Actual Results:  
Get error:
function eval must be called directly, and not by way of a function of another name

Expected Results:  
Let me call eval :)
-> default qa
QA Contact: pschwartau → general
Warning not used anymore.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.