[FFmpeg-devel] [PATCH 1/3] lavformat: Prepare to make avio_enum_protocols const correct

Carl Eugen Hoyos ceffmpeg at gmail.com
Fri Mar 20 23:09:59 EET 2020


Am Fr., 20. März 2020 um 19:33 Uhr schrieb Derek Buitenhuis
<derek.buitenhuis at gmail.com>:
>
> On 21/08/2019 10:04, Andreas Rheinhardt wrote:
> > +#if FF_API_NONCONST_ENUM_PROTOCOLS
> >  const char *avio_enum_protocols(void **opaque, int output)
> > +#else
> > +const char *avio_enum_protocols(const void **opaque, int output)
> > +#endif
>
> Do we actually allow breakage like this (even at major bumps)?
>
> That is, you are not using a new function name, but breaking an existing
> function signature. As far as I know, this is not somthing that we, or
> semver, allow.

We are only breaking it for C++ users, right?

Carl Eugen


More information about the ffmpeg-devel mailing list