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

Issue 366027: Fix case where we treat an unaliased call to eval as an aliased call... (Closed)

Created:
11 years, 1 month ago by Mads Ager (chromium)
Modified:
9 years, 7 months ago
CC:
v8-dev
Visibility:
Public.

Description

Fix case where we treat an unaliased call to eval as an aliased call to eval. BUG=http://code.google.com/p/v8/issues/detail?id=496 Committed: http://code.google.com/p/v8/source/detail?r=3225

Patch Set 1 #

Total comments: 1
Unified diffs Side-by-side diffs Delta from patch set Stats (+46 lines, -2 lines) Patch
M src/scopes.cc View 1 chunk +4 lines, -2 lines 1 comment Download
A test/mjsunit/regress/regress-496.js View 1 chunk +42 lines, -0 lines 0 comments Download

Messages

Total messages: 2 (0 generated)
Mads Ager (chromium)
11 years, 1 month ago (2009-11-05 10:39:26 UTC) #1
Kevin Millikin (Chromium)
11 years, 1 month ago (2009-11-05 11:12:47 UTC) #2
LGTM.

http://codereview.chromium.org/366027/diff/1/3
File src/scopes.cc (right):

http://codereview.chromium.org/366027/diff/1/3#newcode543
Line 543: // the statically resolved (local!) variable belonging to an outer
scope,
Could you delete "(local!)" from this comment?

Powered by Google App Engine
This is Rietveld 408576698