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`_.
+thereby working around the command-line length limits.
Top-Level Classes and Functions
-------------------------------
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, and a
-fourth boolean parameter that enables `response files`_.
+`additional extra text`_ to emit when the ``-help`` option is invoked.
.. _cl::ParseEnvironmentOptions:
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, the optional `additional extra text`_ to emit when the
-``-help`` option is invoked, and the boolean switch that controls whether
-`response files`_ should be read.
+variable to examine, and the optional `additional extra text`_ to emit when the
+``-help`` option is invoked.
``cl::ParseEnvironmentOptions`` will break the environment variable's value up
into words and then process them using `cl::ParseCommandLineOptions`_.