On date Friday 2011-04-08 02:52:13 +0300, aviad rozenhek wrote: > On Thu, Apr 7, 2011 at 23:39, Anton Khirnov <[email protected]> wrote: > > > On Thu, Apr 07, 2011 at 10:25:12PM +0200, Luca Barbato wrote: > > > > Of course it all depends on demand for such a thing, so who wants direct > > access to protocols, please speak up now. > > > > -- > > Anton Khirnov > > > > I want direct access to protocols
+1 (and having the struct public allows to implement a custom protocol). But, if it there is the need to keep the struct private at least when it is "cleaned up", you can: 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). _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
