Documentation for @file for inclusion in other manuals
Mark Mitchell
mark@codesourcery.com
Mon Oct 3 20:13:00 GMT 2005
I just checked in some documentation for @file to binutils. But, then,
I realized that we'll want it in all programs that use expandargv.
So, it seems better to put this in libiberty/response.texi, where it
could be @include'd by those manuals that want to use it? Is it OK to
check this in? Or, do you want to see a formal patch first? Or, is
there some better way to share the user documentation?
===
@item @@@var{file}
Read command-line options from @var{file}. The options read are
inserted in place of the original @@@var{file} option. If @var{file}
does not exist, or cannot be read, then the option will be treated
literally, and not removed.
Options in @var{file} are separated by whitespace. A whitespace
character may be included in an option by surrounding the entire
option in either single or double quotes. Any character (including a
backslash) may be included by prefixing the character to be included
character with a backslash. The @var{file} may itself contain
additional @@@var{file} options; any such options will be processed
recursively.
===
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304
More information about the Gcc-patches
mailing list