On 4/8/11 1:35 PM, Stefano Sabatini wrote:
1) keep the header public but declare that the API is not considered
stable and there is no guarantee of backward compatibility (similar
to what is done with lavfi)
2) keep the header private while the API is reworked
With 1) you still have the possibility to use that API in a custom
application, without the need of brittle hacks (like copying
<private_header> into the application).
I like better option 1, probably adding a guard LIBAV_TRANSIENT_API to
make 100% sure people are aware about it.
lu
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
