> As winapi_check progresses it emits progress messages.
> Unfortunately
> progress messages and regular messages are both sent to
> stderr so that a
> line like the following does not work:
>
> tools/winapi_check/winapi_check --headers 2>&1 | tee headers.txt
>
> The problem is that the resulting headers.txt file contains the
> progress together with lots of ^H. With this patch the
> progress messages
> go to stderr and the regular messages go to stdout and thus
> you can do:
>
> tools/winapi_check/winapi_check --headers >headers.txt
> or
> tools/winapi_check/winapi_check --headers | tee headers.txt
Well, there are an option called --no-progress that can be used.
Like
tools/winapi_check/winapi_check --no-progress --headers 2>
headers.txt
or
tools/winapi_check/winapi_check --no-progress --headers 2>&1 | tee
headers.txt
Or perhaps if you only wants the headers you can do
tools/winapi_check/winapi_check --none --win16 --win32 --headers 2>&1
| tee headers.txt
Anyway, you are right messages should go to STDOUT and
progress should go to STDERR sine it will allow for a
nicer command line syntax as shown by you above.
In short, I support inclusion of the patch. In fact I already have it in my
tree,
so I send it in with my next winapi_check update. Of course Alexandre can
apply your patch in the meantime if he so wishes.
BTW, in the version in _my_ tree --headers has changed name to --prototype
or
rather --headers means that the headers (*.h) files should be analysed
and --prototype means that "no prototype" errors should be reported.
--prototype implies --headers. So watch out in the future.
