Ignore:
Timestamp:
Jun 19, 2011, 8:50:36 PM (14 years ago)
Author:
[email protected]
Message:

2011-06-19 Oliver Hunt <[email protected]>

Reviewed by Sam Weinig.

Correct logic for putting errors on the correct line when handling JSONP
https://bugs.webkit.org/show_bug.cgi?id=62962

Add test case this time

  • fast/js/parser-syntax-check-expected.txt:
  • fast/js/script-tests/parser-syntax-check.js:

2011-06-19 Oliver Hunt <[email protected]>

Reviewed by Sam Weinig.

Correct logic for putting errors on the correct line when handling JSONP
https://bugs.webkit.org/show_bug.cgi?id=62962

Minor fix for the minor fix. *sigh*

  • interpreter/Interpreter.cpp: (JSC::Interpreter::execute):
File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/Source/JavaScriptCore/interpreter/Interpreter.cpp

    r89226 r89228  
    772772                        PropertySlot slot(globalObject);
    773773                        if (!globalObject->getPropertySlot(callFrame, JSONPPath[i].m_pathEntryName, slot)) {
    774                             if (i)
     774                            if (entry)
    775775                                return throwError(callFrame, createUndefinedVariableError(globalObject->globalExec(), JSONPPath[i].m_pathEntryName));
    776776                            goto failedJSONP;
Note: See TracChangeset for help on using the changeset viewer.