Hi all Nicolas wrote an interresting comment about avpriv, and as this better belongs into a new thread, here it is in a new thread
On Sun, Mar 25, 2018 at 03:32:33PM +0200, Nicolas George wrote:
> Josh de Kock (2018-03-23):
[...]
> You can observe just that by the fact that you needed to add an avpriv
> function to let lavd communicate with lavf. Each time an avpriv function
> appears, it shows there is something flawed in the design.
If this is true, in general, then we can improve designs by removing
avpriv_* functions ...
looking at what we have as avprivs, in the tree, i think some of these
could be indeed usefull as public APIs. And we need to already keep them
compatible as they are exported as avpriv too, so making such changes does
indeed in some cases look like a good idea to me
There are some avprivs we have currently though that are quite specific
to format intgernals, i dont think that its always a flaw to use avpriv
functions thus
but i think we should evaluate each of the currently existing avpriv
functions and check if the API wouldnt be usefull to user applications.
And if it wouldnt be better to make it properly public
thx
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
The misfortune of the wise is better than the prosperity of the fool.
-- Epicurus
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
