Support placement new syntax for zone objects and start using it in the parser.

Support placement new syntax for zone objects and start using it in the parser.

[Mads Ager (chromium), 2011-04-01 17:08:38]

LGTM

http://codereview.chromium.org/6771058/diff/3001/src/parser.cc
File src/parser.cc (right):

http://codereview.chromium.org/6771058/diff/3001/src/parser.cc#newcode105
src/parser.cc:105: RegExpTree* atom = new(zone())
RegExpAtom(characters_->ToConstVector());
We have to decide whether we want a space between the new keyword and the
placement. I think I would prefer that:

new (zone()) RegExpAtom(...);

My guess would be that it is not covered by conding standards. In that case I
will leave the choice to you. Based on this code I guess you prefer not to have
the space?

[Vitaly Repeshko, 2011-04-04 06:29:41]

Thanks for the review. You're right, placement new syntax doesn't seem to be
covered by the style guide, but a) the no-space variant is more common in the
chromium sources (including existing usages in v8) and b) if the space is added
it makes the lint unhappy (it confuses "new" with a function call). Landed with
no space.