Reviewers: rossberg,
Message:
The extended mode is entered instead of the strict mode
during parsing when using the strict mode directive
"use strict" and when the the harmony-scoping flag is
active. Will change that once it is fully specified how
the extended mode is entered.
For now I've used the name 'is_strict_or_extended_mode'
for the predicate which tests against non classic modes.
I'm open for suggestions, but IMO it doesn't occur too
often in the source.
Please take a look.
Description:
Introduce extended mode.
Please review this at http://codereview.chromium.org/8417035/
SVN Base: https://v8.googlecode.com/svn/branches/bleeding_edge
Affected files:
M src/accessors.cc
M src/arm/full-codegen-arm.cc
M src/arm/lithium-codegen-arm.cc
M src/arm/stub-cache-arm.cc
M src/ast-inl.h
M src/ast.h
M src/bootstrapper.cc
M src/compilation-cache.h
M src/compilation-cache.cc
M src/compiler.h
M src/compiler.cc
M src/execution.cc
M src/factory.h
M src/factory.cc
M src/full-codegen.h
M src/globals.h
M src/handles.h
M src/heap.cc
M src/ia32/full-codegen-ia32.cc
M src/ia32/lithium-codegen-ia32.cc
M src/ia32/stub-cache-ia32.cc
M src/ic.cc
M src/objects-inl.h
M src/objects.h
M src/objects.cc
M src/parser.h
M src/parser.cc
M src/preparse-data.h
M src/preparser.h
M src/preparser.cc
M src/runtime.cc
M src/scopeinfo.cc
M src/scopes.h
M src/scopes.cc
M src/x64/full-codegen-x64.cc
M src/x64/lithium-codegen-x64.cc
M src/x64/stub-cache-x64.cc
M test/cctest/test-heap.cc
M test/cctest/test-parsing.cc
M test/mjsunit/debug-scopes.js
M test/mjsunit/harmony/block-conflicts.js
M test/mjsunit/harmony/block-for.js
M test/mjsunit/harmony/block-leave.js
M test/mjsunit/harmony/block-let-crankshaft.js
M test/mjsunit/harmony/block-let-declaration.js
M test/mjsunit/harmony/block-let-semantics.js
M test/mjsunit/harmony/block-scoping.js
M test/mjsunit/harmony/debug-blockscopes.js
M test/mjsunit/harmony/debug-evaluate-blockscopes.js
