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

Unified Diff: tools/gn/function_write_file.cc

Issue 2481423002: Convert gn docstrings to C++11 raw strings. (Closed)
Patch Set: Fixes Created 4 years, 1 month ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « tools/gn/function_toolchain_unittest.cc ('k') | tools/gn/functions.cc » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: tools/gn/function_write_file.cc
diff --git a/tools/gn/function_write_file.cc b/tools/gn/function_write_file.cc
index feb1004c3f22d2ef668294e1d1c8d0d6ebf3133d..0e2dd0688026f23d53c0415434aafba32f6a5681 100644
--- a/tools/gn/function_write_file.cc
+++ b/tools/gn/function_write_file.cc
@@ -23,32 +23,32 @@ 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,
« no previous file with comments | « tools/gn/function_toolchain_unittest.cc ('k') | tools/gn/functions.cc » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698