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

Issue 274067: Add string16 support for LowerCaseEqualsASCII, StartsWith, and EndsWith.... (Closed)

Created:
11 years, 2 months ago by darin (slow to review)
Modified:
9 years, 7 months ago
Reviewers:
Matt Perry
CC:
chromium-reviews_googlegroups.com, brettw+cc_chromium.org
Visibility:
Public.

Description

Add string16 support for LowerCaseEqualsASCII, StartsWith, and EndsWith. R=mpcomplete BUG=none TEST=none Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=29209

Patch Set 1 #

Total comments: 3
Unified diffs Side-by-side diffs Delta from patch set Stats (+71 lines, -10 lines) Patch
M base/string_util.h View 4 chunks +15 lines, -0 lines 0 comments Download
M base/string_util.cc View 4 chunks +56 lines, -10 lines 3 comments Download

Messages

Total messages: 4 (0 generated)
darin (slow to review)
11 years, 2 months ago (2009-10-15 19:14:58 UTC) #1
Matt Perry
lgtm http://codereview.chromium.org/274067/diff/1/3 File base/string_util.cc (right): http://codereview.chromium.org/274067/diff/1/3#newcode754 Line 754: #if !defined(WCHAR_T_IS_UTF16) This confused me for a ...
11 years, 2 months ago (2009-10-15 23:06:16 UTC) #2
darin (slow to review)
http://codereview.chromium.org/274067/diff/1/3 File base/string_util.cc (right): http://codereview.chromium.org/274067/diff/1/3#newcode754 Line 754: #if !defined(WCHAR_T_IS_UTF16) On 2009/10/15 23:06:16, Matt Perry wrote: ...
11 years, 2 months ago (2009-10-15 23:13:15 UTC) #3
Matt Perry
11 years, 2 months ago (2009-10-15 23:18:47 UTC) #4
http://codereview.chromium.org/274067/diff/1/3
File base/string_util.cc (right):

http://codereview.chromium.org/274067/diff/1/3#newcode754
Line 754: #if !defined(WCHAR_T_IS_UTF16)
On 2009/10/15 23:13:15, darin wrote:
> On 2009/10/15 23:06:16, Matt Perry wrote:
> > This confused me for a minute. Can you add a comment explaining that the
> wstring
> > definition is used when this define is set? 
> 
> This #if pattern appears throughout this file.  It would be a bit verbose to
> decorate them all, but it wouldn't serve the purpose unless I did.
> 
> How about if i repeated this:
> 
> #if !defined(WCHAR_T_IS_UTF16)  // string16 != wstring

I didn't realize it was a common pattern. In that case, I don't think any
comment is necessary.

Powered by Google App Engine
This is Rietveld 408576698