Fix redefinition of aliased elements in arguments.

Fix redefinition of aliased elements in arguments.

This refactors the way we (re)define elements to perform normalization
and attribute updating at a much deeper level, thereby removing some
bogus special cases in upper runtime layers.

Most element setters take an indicator flag that distinguishes between
setting and defining. Setting of an element causes attributes to remain
unchanged, writability to be checked and callbacks to be called.
Defining of an element causes attributes to be updated and callbacks to
be overridden. The same approach could be taken for properties.

R=svenpanne@chromium.org
BUG=v8:1772
TEST=test262,test262/15.2.3.6-4-333-11

Committed: https://code.google.com/p/v8/source/detail?r=10808

[Sven Panne, 2012-02-23 11:04:20]

LGTM with a nit

https://chromiumcodereview.appspot.com/9443014/diff/1/src/objects.h
File src/objects.h (right):

https://chromiumcodereview.appspot.com/9443014/diff/1/src/objects.h#newcode1354
src/objects.h:1354: // remain unchanged and callbacks to be overridden.
Defining => attributes get updated

[Michael Starzinger, 2012-02-23 11:43:42]

Added new patch set. Landed.

https://chromiumcodereview.appspot.com/9443014/diff/1/src/objects.h
File src/objects.h (right):

https://chromiumcodereview.appspot.com/9443014/diff/1/src/objects.h#newcode1354
src/objects.h:1354: // remain unchanged and callbacks to be overridden.
On 2012/02/23 11:04:20, Sven Panne wrote:
> Defining => attributes get updated

Done.