On Monday 08 October 2007, Julian Seward wrote: > And so you want > to make clear to users which tools are considered production-ready (you > can rely on the output) and those which aren't (you have to be more careful > in interpreting the output).
Ok, in that case a --yes-I-accept-the-disclaimer option that you have to pass via e.g. environment or interactive question during startup would make it more clear to the user that the user should not put too much trust into the report. For me, a mere "exp-" prefix is ambiguous - it can mean that the tool might be unstable, not that it might be incorrect. Dirk ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Valgrind-developers mailing list Valgrind-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-developers
