Lines Matching refs:flags
34 // This file contains the implementation of all our command line flags
60 // global registry, which is where flags defined via DEFINE_foo()
152 // Special flags, type 1: the 'recursive' flags. They set another flag's val.
154 "load flags from file");
156 "set flags from the environment"
159 "set flags from the environment if present");
161 // Special flags, type 2: the 'parsing' flags. They modify how we parse.
165 "with that name. IMPORTANT: flags in this list that have "
185 // There are also 'reporting' flags, in commandlineflags_reporting.cc.
190 // Enables deferred processing of flags in dynamically loaded libraries.
572 // Flags API and wrote directly through the FLAGS_name variable.
647 friend class ::google::FlagSaverImpl; // reads all the flags in order to copy them
872 // handle the 'reporting' flags like --help and --mpm_version.
882 // The argument is the flag-registry to register the parsed flags in
886 // Stage 1: Every time this is called, it reads all flags in argv.
887 // However, it ignores all flags that have been successfully set
896 // Stage 3: validate all the commandline flags that have validators
924 // These are the 'recursive' flags, defined at the top of this file.
925 // Whenever we see these flags on the commandline, we must take action.
941 // Parse a list of (comma-separated) flags.
942 static void ParseFlagList(const char* value, vector<string>* flags) {
958 flags->push_back(string(value, len));
994 // Like getopt(), we permute non-option flags to be at the end.
1067 if (remove_flags) { // Fix up argc and argv by removing command line flags
1146 // The recursive flags, --flagfile and --fromenv and --tryfromenv,
1239 // 3) A list of filenames -- starts a new filenames+flags section
1394 // returns, as strings, all the info about all the flags in
1419 // Now sort the flags, first by filename they occur in, then alphabetically
1585 // This class stores the states of all flags at construct time,
1586 // and restores all flags to that state at destruct time.
1625 // assume no flags were added or deleted from the registry since
1664 // commandline flags into a file/string and read them back
1669 // Note they don't save --flagfile flags (though they do save
1674 const vector<CommandLineFlagInfo>& flags) {
1678 for (i = flags.begin(); i != flags.end(); ++i) {
1685 for (i = flags.begin(); i != flags.end(); ++i) {
1712 // Should we handle --help and such when reading flags from a string? Sure.
1715 // Error. Restore all global flags to their previous values.
1734 vector<CommandLineFlagInfo> flags;
1735 GetAllFlags(&flags);
1738 for (i = flags.begin(); i != flags.end(); ++i) {
1740 flags.erase(i);
1744 fprintf(fp, "%s", TheseCommandlineFlagsIntoString(flags).c_str());
1837 // the parsing of the flags and the printing of any help output.
1847 // When we parse the commandline flags, we'll handle --flagfile,
1851 // those too, as if they were the first flags on the commandline.
1859 // Now get the flags specified on the commandline
1865 // See if any of the unset flags fail their validation checks
1868 if (parser.ReportErrors()) // may cause us to exit on illegal flags
1889 // dlopen, to get the new flags. But you have to explicitly
1891 // of unrecognized flags calling a fatal error.
