On Fri, 23 Oct 2015 01:31:06 +0200
Hendrik Leppkes <[email protected]> wrote:

> On Thu, Oct 22, 2015 at 11:53 PM, Vittorio Giovara
> <[email protected]> wrote:
> > attribute_deprecated triggers a heavy amount of warning in every use
> > of the structure when Libav is compiled with gcc, rather than clang.
> >
> > Move the notice in the documentation section instead.
> >
> > Signed-off-by: Vittorio Giovara <[email protected]>
> > ---
> >  libavcodec/avcodec.h | 4 +---
> >  1 file changed, 1 insertion(+), 3 deletions(-)
> >
> > diff --git a/libavcodec/avcodec.h b/libavcodec/avcodec.h
> > index 0876343..9b832f3 100644
> > --- a/libavcodec/avcodec.h
> > +++ b/libavcodec/avcodec.h
> > @@ -3174,10 +3174,8 @@ typedef struct AVHWAccel {
> >   */
> >
> >  /**
> > - * four components are given, that's all.
> > - * the last component is alpha
> > + * @deprecated use AVFrame or imgutils functions instead
> >   */
> > -attribute_deprecated
> >  typedef struct AVPicture {
> >      uint8_t *data[AV_NUM_DATA_POINTERS];
> >      int linesize[AV_NUM_DATA_POINTERS];     ///< number of bytes per line  
> 
> Didn't we deprecate entire structs before, some different way? Or is
> this the first time that we would run into this issue?
> Anyway, if all functions that take an AVPicture are marked deprecated,
> hopefully people will notice it anyway.

Also, I'd expect the compiler be nice and not warn if deprecated
declarations use other deprecated declarations.
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to