Leo Izen (12022-08-22):
> > > +An API that can be used everywhere a function needs to return a
> > > string, or
> > > +really an arbitrary buffer of bytes, and everywhere code needs to
> > > build a
> > > +string from parts. It needs to be fast and lightweight enough to be
> > > used in
> > > +tight loops, like once per frame, without limiting the size of the
> > 
> > How is that different from open_memstream?
> 
> I'm not sure open_memstream is available on all platforms, in particular I
> think it's missing on MinGW.
> 
> But otherwise, it looks like it, so maybe it makes more sense to just use a
> compatibility shimmy on windows?

open_memstream() does not even qualify for “fast and lightweight enough
to be used in tight loops”, let alone all the features AVWriter has.

Regards,

-- 
  Nicolas George