Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(104)

Issue 226: Make gcc 4.1 happy with NULL in EXPECT_EQ (Closed)

Created:
12 years, 3 months ago by Michael Moss
Modified:
9 years, 7 months ago
CC:
chromium-reviews_googlegroups.com
Visibility:
Public.

Description

Make gcc 4.1 happy with NULL in EXPECT_EQ. This avoids warnings like: src/base/thread_local_unittest.cc:88: warning: passing NULL to non-pointer argument 3 of 'static testing::AssertionResult testing::internal::EqHelper<true>::Compare(const char*, const char*, const T1&, T2*) [with T1 = int, T2 = <unnamed>::ThreadLocalTesterBase]' Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=1716

Patch Set 1 #

Patch Set 2 : '' #

Unified diffs Side-by-side diffs Delta from patch set Stats (+3 lines, -3 lines) Patch
M base/thread_local_unittest.cc View 1 2 chunks +3 lines, -3 lines 0 comments Download

Messages

Total messages: 2 (0 generated)
Michael Moss
12 years, 3 months ago (2008-09-04 06:39:55 UTC) #1
Michael Moss
12 years, 3 months ago (2008-09-04 07:46:20 UTC) #2
Discussed with Dean, and decided to switch back to EXPECT_EQ, forcing NULL to
pointer type. This is more consistent with other EXPECT_EQ uses in Chrome.

Powered by Google App Engine
This is Rietveld 408576698