Remove --harmony implications for incomplete features
authorrossberg@chromium.org <rossberg@chromium.org>
Tue, 4 Nov 2014 16:05:27 +0000 (16:05 +0000)
committerrossberg@chromium.org <rossberg@chromium.org>
Tue, 4 Nov 2014 16:05:44 +0000 (16:05 +0000)
commit0b9a70ade35a13a6142472ef704231923a8ca53f
tree9278d83a4103fb569727beb137d4f1814df0a05b
parent3386da98fb84194a70f18dde23b8fb49f4030857
Remove --harmony implications for incomplete features

This is in preparation for making --harmony and --es-staging synonyms.
The only remaining difference currently is block-scoping, which is still
implied by --harmony, to avoid regressing on a long-available feature.

Also removes the special-casing of --harmony-proxies.

R=adamk@chromium.org
BUG=

Review URL: https://codereview.chromium.org/693153004

Cr-Commit-Position: refs/heads/master@{#25115}
git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@25115 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/bootstrapper.cc
src/flag-definitions.h
test/mjsunit/harmony/classes.js
test/mjsunit/harmony/regress/regress-343928.js