Use assertions to ensure proper use of the osl command line arg API

Stephan says: I don't buy that argument of making things less fragile;
IMO it's that "defensive programming" approach gone wrong, where you
add complexity to mitigate a problem's effects in one place, instead
of fixing the problem itself in the real place. [...] The better
robustification is probably to turn the OSL_TRACE in
osl_getCommandArgCount (sal/osl/unx/process_impl.cxx) into something
stronger like SAL_WARN, assert, or std::abort

Change-Id: I3ba6684b4921eb67c2f4534e29e33056e8a891b3

0 files changed, 0 insertions, 0 deletions