Convert gn docstrings to C++11 raw strings.

tools/gn/function_write_file.cc

 // Copyright (c) 2013 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include <iostream>
 #include <sstream>
 
 #include "base/files/file_util.h"
 #include "base/strings/string_split.h"
 #include "base/strings/string_util.h"
 #include "base/strings/utf_string_conversions.h"
 #include "build/build_config.h"
 #include "tools/gn/err.h"
 #include "tools/gn/filesystem_utils.h"
 #include "tools/gn/functions.h"
 #include "tools/gn/input_file.h"
 #include "tools/gn/parse_tree.h"
 #include "tools/gn/scheduler.h"
 
 namespace functions {
 
 const char kWriteFile[] = "write_file";
 const char kWriteFile_HelpShort[] =
     "write_file: Write a file to disk.";
 const char kWriteFile_Help[] =
-    "write_file: Write a file to disk.\n"
-    "\n"
-    "  write_file(filename, data)\n"
-    "\n"
-    "  If data is a list, the list will be written one-item-per-line with no\n"
-    "  quoting or brackets.\n"
-    "\n"
-    "  If the file exists and the contents are identical to that being\n"
-    "  written, the file will not be updated. This will prevent unnecessary\n"
-    "  rebuilds of targets that depend on this file.\n"
-    "\n"
-    "  One use for write_file is to write a list of inputs to an script\n"
-    "  that might be too long for the command line. However, it is\n"
-    "  preferrable to use response files for this purpose. See\n"
-    "  \"gn help response_file_contents\".\n"
-    "\n"
-    "  TODO(brettw) we probably need an optional third argument to control\n"
-    "  list formatting.\n"
-    "\n"
-    "Arguments\n"
-    "\n"
-    "  filename\n"
-    "      Filename to write. This must be within the output directory.\n"
-    "\n"
-    "  data:\n"
-    "      The list or string to write.\n";
+    R"(write_file: Write a file to disk.
+
+  write_file(filename, data)
+
+  If data is a list, the list will be written one-item-per-line with no quoting
+  or brackets.
+
+  If the file exists and the contents are identical to that being written, the
+  file will not be updated. This will prevent unnecessary rebuilds of targets
+  that depend on this file.
+
+  One use for write_file is to write a list of inputs to an script that might
+  be too long for the command line. However, it is preferrable to use response
+  files for this purpose. See "gn help response_file_contents".
+
+  TODO(brettw) we probably need an optional third argument to control list
+  formatting.
+
+Arguments
+
+  filename
+      Filename to write. This must be within the output directory.
+
+  data
+      The list or string to write.
+)";
 
 Value RunWriteFile(Scope* scope,
                    const FunctionCallNode* function,
                    const std::vector<Value>& args,
                    Err* err) {
   if (args.size() != 2) {
     *err = Err(function->function(), "Wrong number of arguments to write_file",
                "I expected two arguments.");
     return Value();
   }
@@ skipping 32 matching lines @@
       scope->settings()->build_settings()->GetFullPath(source_file);
 
   // Make sure we're not replacing the same contents.
   if (!WriteFileIfChanged(file_path, contents.str(), err))
     *err = Err(function->function(), err->message(), err->help_text());
 
   return Value();
 }
 
 }  // namespace functions