Currently it's difficult to process runtimes' output because stdout and stderr
are reserved to the called program. If e.g. the AWK script "evaluate_statistics.awk"
is used for processing runtimes' output, the following command could be used:
If only the statistics are relevant, the use of a temporary file is complicated.
Could "runtimes" get a new option (e.g. '-s' for "silence") where the output of
the started programs gets ignored, and "runtimes" uses stdout and stderr for
its own purpose? Example:
In this case "runtimes -s somecommand" would completely "silence" the command
by ignoring its stdout and stderr, and runtimes would print its statistics
directly to standard output.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Currently it's difficult to process runtimes' output because stdout and stderr
are reserved to the called program. If e.g. the AWK script "evaluate_statistics.awk"
is used for processing runtimes' output, the following command could be used:
If only the statistics are relevant, the use of a temporary file is complicated.
Could "runtimes" get a new option (e.g. '-s' for "silence") where the output of
the started programs gets ignored, and "runtimes" uses stdout and stderr for
its own purpose? Example:
In this case "runtimes -s somecommand" would completely "silence" the command
by ignoring its stdout and stderr, and runtimes would print its statistics
directly to standard output.