On Sun, 22 May 2011, Justin Ruggles wrote: > I think having this could be misleading, as it would not work as > expected in all cases. The user would have to look at the option list > to know whether the constant name is unique to be sure what is being > returned is correct. So I don't think the patch is worth applying > as-is. If this functionality is really needed then we could make a new > public function (or set of functions) that takes both the parent option > name and the constant option name. This would also be more > user-friendly than av_find_opt() with the unit param since the unit > string can be any unique string and doesn't necessarily match the parent > option name.
Indeed, makes sense. Patch dropped for now then. // Martin _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
