Bug introduced in commit db1354. getopt_long will already have printed
an appropriate error message in case of an invalid/unrecognized option
or an option missing an required argument. So don't print another error
message in that case.
* session.cxx (parse_cmdline): Silently handle '?' case.
}
break;
+ case '?':
+ // Invalid/unrecognized option given or argument required, but
+ // not given. In both cases getopt_long() will have printed the
+ // appropriate error message to stderr already.
+ return 1;
+ break;
+
default:
// NOTREACHED unless one added a getopt option but not a corresponding switch/case:
cerr << "Unhandled argument code " << (char)grc << endl;