Conversation
Fixes issue szatmary#55
|
Polluting to stderr from a library isn't much better than polluting stdout. A real solution would be to have an API to provide a logging callback and opaque user pointer to pass to that callback. |
|
If a program outputs actual data to stdout, then "polluting" stderr is the only option. This fix was made because the example program flv+srt can output the processed media stream to stdout. If stdout also contains debug messages, the resulting stream will be invalid. |
|
This is untrue. stderr is not the only option - did you read what I wrote? I provided exactly what the correct option is. |
|
Yes, you are right. I should have rewritten the library that I used today for the first time, that I needed for a small thing, by implementing an API with callbacks and user pointers. Thank you for pointing out what is exactly the correct option. |
|
I merely contested that it was the "only" option, which is what you said. Please settle down. I think if you have no interest in correcting the behavior, it is preferable to comment out or remove them instead - @szatmary's approval pending, of course. |
Fixes issue #55