[x265] [PATCH] List: Basic List Operations To Replace std::list

Derek Buitenhuis derek.buitenhuis at gmail.com
Thu Sep 12 12:56:16 CEST 2013


On 9/12/2013 11:46 AM, Steve Borho wrote:
> The short term issue is that STL makes integration into applications that were compiled by a different compiler pretty fragile, and just having the same class not in namespace std makes those problems go away.

>From what I understand, std::list is very well supported in all major C++ compilers.

> The medium term issue is that the encoder still has logic that inserts NALs between other NALs in the access unit, and so we can't simply concatenate NALs as we generate them, we still need a list structure.  And since we also need a list structure for the picture lists, this is the one place in the encoder (outside of vector primitives) where templating would be somewhat sane.

I'm not a C++ guy, but couldn't you use something like std::vector's insert() method?
Perhaps that would be slow? Don't know. std::vector is very well supported.

> Long term.. I haven't looked at how this is handled in x264.  Advice welcome.

You should ask Jason, Anton, or Kieran.

- Derek


More information about the x265-devel mailing list