[FFmpeg-devel] _t POSIX namespace issues

Måns Rullgård mans
Thu Dec 11 11:49:46 CET 2008

Jason Garrett-Glaser wrote:
> On Thu, Dec 11, 2008 at 1:38 AM, M?ns Rullg?rd <mans at mansr.com> wrote:
>> "Jason Garrett-Glaser" <darkshikari at gmail.com> writes:
>>>> Jason Garrett-Glaser:
>>>> libavcodec/libx264.c:    x264_nal_t *nal;
>>>> libavcodec/libx264.c:    x264_param_t params;
>>>> libavcodec/libx264.c:    x264_picture_t pic;
>>> Are you suggesting that we change the x264 API because of this?
>>> Because those structs are defined in x264.h itself, not in libavcodec.
>> Are you suggesting x264 is above the law?
> No, I'm suggesting that you're going to have to convince Loren that
> it's worth breaking API compatibility to "fix" something that I
> couldn't care less about if I tried.

You should care about standards.  In this particular case, a name clash
on current or future systems seems unlikely, so breaking the API just for
this is not warranted.  I would, however, consider fixing it next time
the API changes incompatibly for some other reason.

Speeding is illegal, even when no other cars are on the road.

> Plus, you went on to say in your next email:
>> Those are probably defined by the xvid headers.  Not much we can do about
>> that.
> What, is xvid above the law, while x264 isn't?

I meant that we, the FFmpeg devs, can't do much about xvid headers.  My
original response was to you as an x264 developer, as you appeared to
be speaking in this capacity rather than from an FFmpeg point of view.

M?ns Rullg?rd
mans at mansr.com

More information about the ffmpeg-devel mailing list