Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(194)

Unified Diff: src/parser.cc

Issue 1279203002: Delete outdated comment about a bug which was fixed three years ago (Closed) Base URL: https://chromium.googlesource.com/v8/v8.git@master
Patch Set: Description update Created 5 years, 4 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: src/parser.cc
diff --git a/src/parser.cc b/src/parser.cc
index 45202cb3a82b922c7d487061cfff03578cc3a3c9..8299e2974467921eb0ef17b43f06f187be587c4d 100644
--- a/src/parser.cc
+++ b/src/parser.cc
@@ -1337,10 +1337,7 @@ void* Parser::ParseStatementList(ZoneList<Statement*>* body, int end_token,
// Because declarations in strict eval code don't leak into the scope
// of the eval call, it is likely that functions declared in strict
// eval code will be used within the eval code, so lazy parsing is
- // probably not a win. Also, resolution of "var" bindings defined in
- // strict eval code from within nested functions is currently broken
- // with the pre-parser; lazy parsing of strict eval code causes
- // regress/regress-crbug-135066.js to fail.
+ // probably not a win.
if (scope_->is_eval_scope()) mode_ = PARSE_EAGERLY;
} else if (literal->raw_value()->AsString() ==
ast_value_factory()->use_asm_string() &&
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698