Re: [FFmpeg-devel] [PATCH 2/2] doc/plans: add AVWriter

From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] doc/plans: add AVWriter
Date: Mon, 22 Aug 2022 16:59:42 +0200
Message-ID: <YwOZ3pXNty1xzxEG@phare.normalesup.org> (raw)
In-Reply-To: <bcac6bf7-ca75-b91a-0dc6-be08fa65f3e3@gmail.com>

[-- Attachment #1.1: Type: text/plain, Size: 843 bytes --]

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

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".