On 11/09/16 10:45, Nicolas George wrote:
Le sextidi 26 fructidor, an CCXXIV, Sven C. Dack a écrit :
Error messages go to stderr and one sometimes parses these to respond to an
error.
This is bogus and should not be considered a reason for design decisions.
If there are cases where this is actually necessary, then report them and we
can reflect on a correct solution.
No, it's not bogus. It's what sometimes must be done. For example, just this
morning did I again have to pipe the output of ffprobe through "|&" because it
likes to print its findings to stderr and not simply stdout. Not meaning to
derail the topic, but to make a point close "to home".
All I am really saying is that I don't quite agree with Carl. However seeing how
you feel so strongly about what to put into ffserver are you volunteering to
become it's new maintainer (... congrats!).
If one doesn't want to be its maintainer than I don't see how one can afford to
have this opinion. Rather should one follow the general coding rule of FFmpeg to
keep changes minimal and to check if these cannot be made even smaller.
Sven
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
