From beb4d8293d5311c4581fd3d914f865e358af53a5 Mon Sep 17 00:00:00 2001
From: Mikhail Glushenkov Some systems, such as certain variants of Microsoft Windows and
+some older Unices have a relatively low limit on command-line
+length. It is therefore customary to use the so-called 'response
+files' to circumvent this restriction. These files are mentioned on
+the command-line (using the "@file") syntax. The program reads these
+files and inserts the contents into argv, thereby working around the
+command-line length limits. Response files are enabled by an optional
+fourth argument to
+cl::ParseEnvironmentOptions
+and
+cl::ParseCommandLineOptions.
+ The cl::ParseCommandLineOptions function requires two parameters
(argc and argv), but may also take an optional third parameter
which holds additional extra text to emit when the
---help option is invoked.
It takes three parameters: the name of the program (since argv may +
It takes four parameters: the name of the program (since argv may not be available, it can't just look in argv[0]), the name of the -environment variable to examine, and the optional +environment variable to examine, the optional additional extra text to emit when the ---help option is invoked.
+--help option is invoked, and the boolean +switch that controls whether reponse files +should be read.cl::ParseEnvironmentOptions will break the environment variable's value up into words and then process them using -- cgit v1.1