mirror of
https://github.com/nodejs/node.git
synced 2025-05-15 17:35:26 +00:00

Pick up the latest branch-head for V8 5.1. This branch brings in improved language support and performance improvements. For full details: http://v8project.blogspot.com/2016/04/v8-release-51.html * Picks up the latest branch head for 5.1 [1] * Edit v8 gitignore to allow trace_event copy * Update V8 DEP trace_event as per deps/v8/DEPS [2] [1] https://chromium.googlesource.com/v8/v8.git/+/dc81244 [2] https://chromium.googlesource.com/chromium/src/base/trace_event/common/+/c8c8665 PR-URL: https://github.com/nodejs/node/pull/7016 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
25 lines
859 B
JavaScript
25 lines
859 B
JavaScript
// Copyright 2015 the V8 project authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style license that can be
|
|
// found in the LICENSE file.
|
|
|
|
// Before Unicode RegExps are shipped, we shouldn't have the 'unicode'
|
|
// property on RegExp.prototype, or read it from 'flags'.
|
|
// mjsunit/es6/regexp-flags tests that the property is there when the
|
|
// flag is on.
|
|
|
|
// Flags: --no-harmony-unicode-regexps
|
|
|
|
'use strict';
|
|
|
|
assertFalse(RegExp.prototype.hasOwnProperty('unicode'));
|
|
|
|
// If we were going to be really strict, we could have a test like this,
|
|
// with the assertTrue replaced by assertFalse, since flags shouldn't
|
|
// Get the 'unicode' property. However, it is probably OK to omit this
|
|
// detailed fix.
|
|
var x = /a/;
|
|
var y = false;
|
|
Object.defineProperty(x, 'unicode', { get() { y = true; } });
|
|
assertEquals("", x.flags);
|
|
assertTrue(y);
|