On Thu, 15 Nov 2007, Josef Weidendorfer wrote: > The "global single option" was meant to be about the output file only. > Of course there also is a log output that already can be redirected > with "--log-file". But we currently do not have a per-tool option for the log > output of each tool. Why do we want different options to specify the output > file of each tool then?
Ok, I think you're suggesting we have just two options, something like: --log-file: for logging output, eg. what normally goes to stderr --out-file: for tool-specific file output, eg. Cachegrind/Massif I find --out-file confusing. The difference with --log-file is not immediately clear. Also, what about tools that don't create a file, like Memcheck -- is --out-file ignored? Should it cause an abort if it's used? I think having options that all tools must implement is not a good idea. We already have some (eg. -v) but I'd like to avoid more. In comparison, if we have a --cachegrind-out-file option, it's very clear what it does, particularly if the default name is "cachegrind.out.<pid>". Nick ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Valgrind-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-developers
