Issue 10689134: Correctly report octal literals in strict mode when preparsing.

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 10689134: Correctly report octal literals in strict mode when preparsing. (Closed)

Created:
8 years, 5 months ago by Yang

Modified:
8 years, 5 months ago

Reviewers:
Michael Starzinger

CC:
v8-dev

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

Visibility:
Public.

Correctly report octal literals in strict mode when preparsing. SingletonLogger::LogMessage did not work as advertised and overwrote existing message. R=mstarzinger@chromium.org BUG=v8:2220 TEST=test-parsing/PreparserStrictOctal Committed: https://code.google.com/p/v8/source/detail?r=12031

Created: 8 years, 5 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+24 lines, -0 lines)			Patch
	M	src/parser.cc	View		1 chunk	+1 line, -0 lines	0 comments	Download
	M	test/cctest/test-parsing.cc	View		1 chunk	+23 lines, -0 lines	0 comments	Download

Total messages: 2 (0 generated)

Michael Starzinger

8 years, 5 months ago (2012-07-10 12:14:20 UTC) #2

LGTM. You could prefix the test name in the CL description with "test-parsing/"
or "cctest/test-parsing/".