avoid using NULL in varadic function for cmdline parsing

cppcheck reports:
(portability) Passing NULL after the last typed argument to a variadic
function leads to undefined behaviour.

We don't ship on any platform which has this as undefined behaviour
through – or it would be pretty well defined "bad" behaviour which
always works, so even through UB is a trigger word, its hardly
noteworthy as a change (and as a bonus the scanners of gcc/clang
don't consider it UB).

The commonly accepted method of fixing that seems to be (const
char*)NULL, but it is in fact much simpler to just switch to the varadic
functions C++ provides resolving the warning and reducing code.

Reported-By: cppcheck
Gbp-Dch: Ignore

0 files changed, 0 insertions, 0 deletions