L'octidi 8 ventôse, an CCXXV, Mark Thompson a écrit : > And what would the user conclude from that message? Have they done > something incorrectly? If so, what? Or is it a bug in the filter? > All of these messages pretty much require reading the source code and > looking at the documentation for the relevant libmfx function to > determine what they mean. (Well, maybe not "out of memory".)
> I disagree. For normal output, yes, this sort of thing is unhelpful. > For fatal error cases, precise information such as error codes should > be provided so that someone reading the source code can determine > exactly what the error was and where it happened. Anything above the verbose level is meant for users, not just developers. If reading the source code is necessary to understand it, then you are doing something seriously wrong. If the error results from invalid parameters set by the user, then the error message should say so, possibly stating what parameter and its acceptable values. If the error results from external (hardware or system) problems, then the error message should say so, pointing to the cause of the problem. Otherwise, the error should clearly state that it is a BUG, and suggest the user to report it, along with diagnostics relevant for the developers obtained at loglevel debug. Regards, -- Nicolas George
signature.asc
Description: Digital signature
_______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
