Issue 8561011: Avoid explicitly using built-in new operator where possible to appease VS compiler.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 8561011: Avoid explicitly using built-in new operator where possible to appease VS compiler. (Closed)

Created:
9 years, 1 month ago by Yang

Modified:
9 years, 1 month ago

Reviewers:
Michael Starzinger

CC:
v8-dev

Base URL:
https://v8.googlecode.com/svn/branches/bleeding_edge

Visibility:
Public.

Avoid explicitly using built-in new operator where possible to appease Windows build. Committed: http://code.google.com/p/v8/source/detail?r=10028

Created: 9 years, 1 month ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Stats (+5 lines, -4 lines)			Patch
M	src/elements.cc	View	1 chunk	+1 line, -1 line	0 comments	Download
M	src/extensions/gc-extension.cc	View	1 chunk	+2 lines, -1 line	0 comments	Download
M	src/hashmap.cc	View	1 chunk	+1 line, -1 line	0 comments	Download
M	src/scopes.cc	View	1 chunk	+1 line, -1 line	0 comments	Download

Total messages: 2 (0 generated)

Yang

Please take a look. Weird Visual Studio behavior. Some cctests crash when using '::new' instead ...

9 years, 1 month ago (2011-11-18 11:03:08 UTC) #1

LGTM.