From 2f6cb866d615d6240a18c7535c994c6bb93b1ba5 Mon Sep 17 00:00:00 2001 From: Ivan Penkov Date: Mon, 7 Nov 2016 19:37:19 -0500 Subject: Allow compiling the google-breakpad code using a global ::string class instead of std::string. For more details take a look at common/using_std_string.h BUG= Change-Id: Ifebfc57f691ef3a3bef8cfed7106c567985edffc Reviewed-on: https://chromium-review.googlesource.com/399738 Reviewed-by: Mark Mentovai --- src/common/dwarf_cfi_to_module.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/common/dwarf_cfi_to_module.h') diff --git a/src/common/dwarf_cfi_to_module.h b/src/common/dwarf_cfi_to_module.h index 084b8f5a..a5302e15 100644 --- a/src/common/dwarf_cfi_to_module.h +++ b/src/common/dwarf_cfi_to_module.h @@ -181,7 +181,7 @@ class DwarfCFIToModule: public CallFrameInfo::Handler { // The names of the return address and canonical frame address. Putting // these here instead of using string literals allows us to share their - // texts in reference-counted std::string implementations (all the + // texts in reference-counted string implementations (all the // popular ones). Many, many rules cite these strings. string cfa_name_, ra_name_; @@ -189,7 +189,7 @@ class DwarfCFIToModule: public CallFrameInfo::Handler { // our data structures, insert it into this set, and then use the string // from the set. // - // Because std::string uses reference counting internally, simply using + // Because string uses reference counting internally, simply using // strings from this set, even if passed by value, assigned, or held // directly in structures and containers (map, for example), // causes those strings to share a single instance of each distinct piece -- cgit v1.2.1