Re: [Supertuxkart-devel] Error logging to file default behavior

[<coz...@gm...>]

Hi list,

> But I added command line options :)  It's fine with me to change the default

Yep I noticed those afterwards :)

[Joerg]
> behaviour, since launchers can easily add the --log=file command line option
> (once changed, your chosen option  will be stored in the config file anyway, so
> I forgot about this as well, since my default obviously is writing to stderr.
> We could add a warning written to stderr/out stating in which files the messages
> will be written (if this option is selected).
[Paul]
> In my view, the default behaviour should be changed to write to stderr,
> and I think Joerg's suggestion of a warning when errors are being logged
> to file is a good one.  I could submit a patch for this if it is wanted,
> and correct the default behaviour too, it might save one of you about a
> minute XD.

Since our code right now is unstable and it's just one line of
difference, we could keep the default to stderr, and change it when
making packages.


> @coz, Sorry for your wasted hour on a virtual bug hunt:(

Don't worry, it was just one hour, thought it's was quite a surprise
that my problem wasn't caused by the code I just wrote :)


Another thing: I remember that Joerg wrote that he couldn't find a way
to check if opening the file assigned as the output of std::cerr was
successful; so, if everyone is fine with it I'll apply the patch and
add a line of text that mentions that the cerr file doesn't outputs
errors when opening fails.

-Coz