[FFmpeg-devel] [RFC] The meaning of AVERROR_NOTSUPP

Stefano Sabatini stefano.sabatini-lala
Sun Apr 18 21:27:25 CEST 2010


On date Wednesday 2010-04-14 01:58:41 +0200, Stefano Sabatini encoded:
> On date Saturday 2010-04-03 13:31:29 +0200, Stefano Sabatini encoded:
> > On date Saturday 2010-04-03 12:36:01 +0200, Michael Niedermayer encoded:
> [...]
> > > Feature not implemented
> > > and
> > > Implementing this feature is welcome
> > > 
> > > are 2 seperate things
> > > 
> > > similarly
> > > 
> > > "not implementable"
> > > "requested operation nonsensical"
> > > "we dont want this implemented"
> > > "disabled at compile time, rerun configure"
> > > 
> > > are all semantically different
> > > 
> > > also you cannot redefine the POSIX error codes to mean something else than
> > > they mean.
> > 
> > So taking into account the considerations of Howard and yours, it
> > seems that we can agree on simply dropping AVERROR_NOTSUPP and use
> > AVERROR(ENOSYS) instead.
> > 
> > We'll use AVERROR_PATCHWELCOME when a feature is not implemented and
> > we want and can implement it, and we'll use AVERROR(ENOSYS) in all the
> > other cases (feature non-implementable, requested operation
> > nonsensical, feature implementable but we don't want to implement it,
> > feature disabled at compile time etc...).
> [...]
> 
> Ping.

Patch updated.
-- 
FFmpeg = Funny and Fantastic Mean Peaceful Elitist God



More information about the ffmpeg-devel mailing list