From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 86DEB403D5 for ; Mon, 22 Aug 2022 14:59:51 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id C12E468B9E3; Mon, 22 Aug 2022 17:59:49 +0300 (EEST) Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 6DA1668B559 for ; Mon, 22 Aug 2022 17:59:43 +0300 (EEST) X-ENS-nef-client: 129.199.129.80 ( name = phare.normalesup.org ) Received: from phare.normalesup.org (phare.normalesup.org [129.199.129.80]) by nef.ens.fr (8.14.4/1.01.28121999) with ESMTP id 27MExgsj010533 for ; Mon, 22 Aug 2022 16:59:42 +0200 Received: by phare.normalesup.org (Postfix, from userid 1001) id 7E2FBE0101; Mon, 22 Aug 2022 16:59:42 +0200 (CEST) Date: Mon, 22 Aug 2022 16:59:42 +0200 From: Nicolas George To: FFmpeg development discussions and patches Message-ID: References: <20220817214932.42351-1-george@nsup.org> <20220817214932.42351-2-george@nsup.org> MIME-Version: 1.0 In-Reply-To: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (nef.ens.fr [129.199.96.32]); Mon, 22 Aug 2022 16:59:42 +0200 (CEST) Subject: Re: [FFmpeg-devel] [PATCH 2/2] doc/plans: add AVWriter X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: multipart/mixed; boundary="===============8467082495645596600==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============8467082495645596600== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="rqo8faEB91qd8yuk" Content-Disposition: inline --rqo8faEB91qd8yuk Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 > >=20 > > How is that different from open_memstream? >=20 > I'm not sure open_memstream is available on all platforms, in particular I > think it's missing on MinGW. >=20 > 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 =E2=80=9Cfast and lightweight en= ough to be used in tight loops=E2=80=9D, let alone all the features AVWriter has. Regards, --=20 Nicolas George --rqo8faEB91qd8yuk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE6ooRQGBoNzw0KnwPcZVLI8pNxgwFAmMDmdwACgkQcZVLI8pN xgxoFA/9HkxVHFdfrTbALLvVYOZeGHBlpp3h+qMcObUL1y55GDVGu65n3Iuu3EUw nLc9bmx2FlfiWBXDu5YfvNv3KbPWIJ7h+7zifXu2xGBbSRc+6+s2DARiANCly74g z2NP3eVvgXud051xcp2uwnPOXe1HRPhYvUce6WnGq9Z72yQsjcCzHFk86rPU3vCc qXJP/gQGaAuGfA0Z9KIPVJVfhAW2P/4OwQmDB8fKXCX96B3PsAer59wBflRbUavV Ie4MQreiNI6xjcrnvoWCopFklfruL7MI5lLZ4oEQGKdM1LACkMAorGC58+akAdH/ vuz+bgaeM+0jPWjzxuwjN06nvqAJOueFC6IYFw1bPZvfyGCZPaDnlyTKDdvx8Xj/ 21ZmZihw53hSOV5O+iGZDwUy01iGSueehCeHV2pIrkKecRYMr+Khd2amzXYxEi8R UX2veJeLQg5kdTmVTbM34UOTJbfiRj2mbuVqtzUjQ/V+gs7s4lYrjC02Bc8pDfd9 yTbkKG2GyuHMKFCx48RYN9riH2S2l5jXkjuMUGAw0grozJMizZB55gH1Czhyx0q0 o3xWlbKFlhaA5sHSPpk0dxWsk6+KfMCekvpHDJZ7cRK9Z41mZsZ+bUZfUZfZLqtc lyXUty5zGDmLVcN8GGQY85mFPD3poNJ/f+MILy1YYScJ1woRPDg= =daGx -----END PGP SIGNATURE----- --rqo8faEB91qd8yuk-- --===============8467082495645596600== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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". --===============8467082495645596600==--