Issue 149033003: Apply automatic range checks to CC enum types across IPC.

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 149033003: Apply automatic range checks to CC enum types across IPC. (Closed)

Created:
6 years, 10 months ago by Tom Sepez

Modified:
6 years, 10 months ago

Reviewers:
piman

CC:
chromium-reviews, joi+watch-content_chromium.org, darin-cc_chromium.org, cc-bugs_chromium.org, jam

Base URL:
svn://svn.chromium.org/chrome/trunk/src

Visibility:
Public.

Apply automatic range checks to CC enum types across IPC. This is part of a long-running background task to remove the remaining uses of the unchecked IPC_ENUM_TRAITS() macro. BUG=246708 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=247569

Created: 6 years, 10 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Stats (+9 lines, -4 lines)			Patch
M	cc/output/filter_operation.h	View	1 chunk	+1 line, -0 lines	0 comments	Download
M	cc/quads/draw_quad.h	View	1 chunk	+1 line, -0 lines	0 comments	Download
M	cc/quads/io_surface_draw_quad.h	View	1 chunk	+2 lines, -1 line	0 comments	Download
M	content/common/cc_messages.h	View	1 chunk	+5 lines, -3 lines	0 comments	Download

Total messages: 4 (0 generated)

commit-bot: I haz the power

CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/tsepez@chromium.org/149033003/1

6 years, 10 months ago (2014-01-28 21:20:36 UTC) #3

Message was sent while issue was closed.

Change committed as 247569