AuroraMiddleware/v8
1
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity

[modules] Ignore the surrounding script scope.

Browse Source 
This is more consistent with how we handle eval scripts.

R=jochen@chromium.org
BUG=v8:1569

Review-Url: https://codereview.chromium.org/2289293006
Cr-Commit-Position: refs/heads/master@{#39069}
This commit is contained in:
neis 2016-09-01 02:16:10 -07:00 committed by Commit bot
parent 9d818bea60
commit b3b574cd8c
1 changed files with 0 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/ast/scopes.cc
View File

@ -461,12 +461,6 @@ void DeclarationScope::Analyze(ParseInfo* info, AnalyzeMode mode) {
scope->outer_scope()->scope_type() == SCRIPT_SCOPE || scope->outer_scope()->scope_type() == SCRIPT_SCOPE ||
scope->outer_scope()->already_resolved_); scope->outer_scope()->already_resolved_);
// For modules, we want to start variable allocation at the surrounding script
// scope.
if (scope->is_module_scope()) {
scope = scope->outer_scope()->AsDeclarationScope();
}
scope->AllocateVariables(info, mode); scope->AllocateVariables(info, mode);
#ifdef DEBUG #ifdef DEBUG