On Mon, Jul 9, 2012 at 2:40 AM, Nathan <[email protected]> wrote: > On Sat, Jul 7, 2012 at 1:36 AM, Richard Jones <[email protected]> wrote: >> Indeed - the whole point of avbin though is ABI stability. Perhaps you could >> even stick with the old API and just include a reference to libav in the >> version info? > > Unfortunately, sticking with the old API isn't possible in this case. > The old API returns an integer which used to represent SVN revision > number. Any sane representation of release version number (0.6.6) or > git commit (123abc456...) requires returning a string. 6 years > without an API change...that's pretty awesome. :-) > > On Fri, Jul 6, 2012 at 11:02 PM, anatoly techtonik <[email protected]> > wrote: >> If it is not clear which lib are you going to stick with, maybe it's better >> to use avbin_get_backend_type() and avbin_get_backend_version()? > > That's an excellent idea. I think we can even take that a bit further! > > How about this set of functions? > > + avbin_get_backend_name() ("Libav") > + avbin_get_backend_version() ("0.6.6") > + avbin_get_backend_repo() ("https://github.com/AVbin/libav.git";) > + avbin_get_backend_commit() ("123abc456def...")
The last two are too excessive - will needlessly bloat the API. avbin_get_backend_version(details=True) can return "%s %s %s %s" with all this information. > Those functions would be pretty flexible and not require future renaming. > > I added that as issue 24: > > https://github.com/AVbin/AVbin/issues/24 -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en.
