Feature request: Our Keil C166 compiler does not make a distinction between standard output or standard error. It would be nice if error/warning messages would be displayed on standard error. This make it easier to redirect output, handle logging in our build environment, etc. Seems like a simple file descriptor adjustment and existing users/tools won't notice the difference.
I'm not sure if the latest version (6.x) supports this already.
Kind rergards, Joost Leeuwesteijn
If nobody would notice the difference, what could possibly be the point of changing the behaviour?
And honestly, I can't figure out how redirecting stderr could ever be easier than redirecting stdout. Or, for that matter, redirecting stdout directly to stderr, if that's what you want to do:
c166 [...arguments...] 1>&2
I was only trying to predict the impact on current users. There's no change in behaviour for them. But now I realize I was wrong about that. When people currently redirect only stdout, it would go wrong when the compiler would make use of stderr.
And honestly, I can't figure out how redirecting stderr could ever be easier than redirecting stdout. Or, for that matter, redirecting stdout directly to stderr, if that's what you want to do: c166 [...arguments...] 1>&2
My point was that the Keil compiler does not even use stderr (as far as I know). But there are cases when making a distinction between stdout and stderr can be useful. In our case, we're not interested in the normal output, only in the warnings/errors. But at the moment there's no way to redirect only one of them, unlike alot of other compilers/tools.
Regards, Joost Leeuwesteijn