[FFmpeg-devel] [PATCH] remove MAX_STREAMS check from mms.c

Ronald S. Bultje rsbultje
Mon Oct 4 16:07:31 CEST 2010


On Mon, Oct 4, 2010 at 9:02 AM, Aurelien Jacobs <aurel at gnuage.org> wrote:
> On Sun, Oct 03, 2010 at 05:09:10PM -0400, Ronald S. Bultje wrote:
>> On Sun, Oct 3, 2010 at 5:01 PM, Aurelien Jacobs <aurel at gnuage.org> wrote:
>> > The MAX_STREAMS check in mms.c looks useless with the new API. Attached
>> > patch just drop it.
>> > mms.c is the last user of MAX_STREAMS in lavf, and I would like to get
>> > ride of it soon.
>> http://archives.free.net.ph/message/20100812.225254.fc8cfbcf.ca.html
> Ooops... I thought there was already a discussion about this but I
> couldn't find it anymore...
> Well, OK. Fine with me. The demuxer can have its own internal safty
> check. But this have to stay inside the demuxer itself, so that the
> value can be tuned depending on the characteristics of the format or the
> demuxer itself without impacting any other code.
> Patch attached.
> +#define MMS_MAX_STREAMS 256    /* arbitrary sanity check value */

Doxy, dude. :-). Otherwise fine with me.


More information about the ffmpeg-devel mailing list