[Mxflib-developers] Re: getchar() before exit...

[Oliver M. <ol...@me...>]

Fine on making default not getchar(), providing an option can reenable it.=
=0D
=0D
I was aiming for the following other behaviours consistet across all apps:=
=0D
=0D
-q	quiet:=0D
	never writes to stdout=0D
	writes errors to stderr=0D
	sets exit code on errors and warnings=0D
=0D
(none)default:=0D
	writes sparsely to stdout=0D
	writes errors warnings and config to stderr=0D
	sets exit code on errors and warnings=0D
=0D
-v	verbose:=0D
	writes verbosely to stdout=0D
	writes errors warnings and config to stderr=0D
	sets exit code on errors and warnings=0D
=0D
Questions: is the proposed -z orthogonal to this? Or could it be seen as a =
"very verbose" (-vv) level? My vote would be for -vv=0D
=0D
Another: how does this relate to #ifdef MXFLIB_DEBUG and the mxflib::debug(=
) function? The present code seems to imply that debug =0D
messages are only output by mxflib::debug() if both -v and MXFLIB_DEBUG. Is=
 that what we want?=0D
=0D
Should mxflib::debug use vfprintf(stderr, Fmt, args)?=0D
Should mxflib::warning use vfprintf(stderr, Fmt, args)?=0D
Should mxflib::error use vfprintf(stderr, Fmt, args)?=0D
=0D
thanks=0D
Oliver=0D