In the case where there is a sub_command, we execute this code:
if (sub_cmd_obj != nullptr) {
// Now call CommandObject::Execute to process and options in
// 'rest_of_line'. From there the command-specific version of Execute
will
// be called, with the processed arguments.
args
> (of those, 7 print the *wrong* function name)
I think this is the best argument for automating the source information as
much as possible. Refactoring moves stretches of code into new functions.
Log lines get copy and pasted. Like comments, the fixed text in the log
lines easily gets out of da
Hello again,
I have updated the example code to reflect some of the results from
this discussion. I think we are generally converging XXX, I am going
to try to summarize it here, to see if we have any issues left to
discuss.
- everyone seemed to prefer the formatv-based api, so that should be
the
