[FFmpeg-cvslog] r22715 - trunk/libavcodec/bitstream.c

[Måns Rullgård]

Uoti Urpala <uoti.urpala at pp1.inet.fi> writes:

>> > Otoh, there are systems with much slower malloc (OSX?).
>> 
>> They can blame themselves.  If it's really important to someone,
>> linking ffmpeg with a different malloc is trivial.
>
> Is there a reason why they should more "blame themselves" than people

They chose to use it.  They get to live the consequences.

> running systems that have problems with the arrays on stack?

Variable-length arrays on the stack are inherently unsafe.  You can't
possibly know where your stack ends, so no checking will ever be
sufficient.

> In general malloc will perform worse and result in more complex and
> fragile code. Even if you add explicit sanity/safety checks for all
> stack arrays the result will be simpler and more robust than with
> malloc.

You're only saying that to contradict me.  I will not entertain your
little troll further.

-- 
M?ns Rullg?rd
mans at mansr.com