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 93F5748D0E for ; Fri, 24 May 2024 01:51:04 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id B55AC68D547; Fri, 24 May 2024 04:51:01 +0300 (EEST) Received: from relay2-d.mail.gandi.net (relay2-d.mail.gandi.net [217.70.183.194]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 7E82268D521 for ; Fri, 24 May 2024 04:50:55 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id 0CFE540004 for ; Fri, 24 May 2024 01:50:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1716515454; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=CfqxW4zB2JkTD5zTVPUcWxmWeT4kE/wG9cZOfKhnMaA=; b=hrCaIgqYZuvmsduP4SJuqbikcA/EmW4/3iPO+dfL7CVzCGhWPhKHSj0tJccpX9bcdKA33a iazWQ9l20vTOHrqdCebCHYBbRgAKAqN+dQHMVDDUkQfq0FfnyPxlpcAlOlXrL2Uh6YKZk+ PO/lkop90ID+S1VxQX66V2BCpYjpdSHk2tFuG3h5+fv3/PPyTd9NV27JSQNwTop97NC8Gm QmRpCFar24V3IfO+9eFS9S9VIR6fsS35xB2FQNSiJrWOrQdXl1kjuXLG12Pg4zDoGhnSjD Q3ZrpJw3PqeoNB8PlIiMvUsCJopHVCcxxgm4dOBhVXa//KwynJ7jxvfcglEuAQ== Date: Fri, 24 May 2024 03:50:52 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20240524015052.GX2821752@pb2> References: <20240523200116.740461-1-ffmpeg-devel@pileofstuff.org> MIME-Version: 1.0 In-Reply-To: <20240523200116.740461-1-ffmpeg-devel@pileofstuff.org> X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] [PATCH v5 0/4] Explain what "context" means 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="===============5183310997425639244==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============5183310997425639244== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="g3IWFuR7/O9KKcN6" Content-Disposition: inline --g3IWFuR7/O9KKcN6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 23, 2024 at 09:00:39PM +0100, Andrew Sayers wrote: > NOTE: this patchset depends on [1], and should not be applied before that. >=20 > I think it's important to guide readers between parts of FFmpeg, because > learning how the pieces of the puzzle fit together is a big part of the > newbie experience. So this patchset replaces the "@ref Context for foo" > statements in public structs with "@see" blocks, giving us a hook we can > hang more links on in future. >=20 > That said, there's a rule against internal links from private structs, > so I've removed the @ref's from them. By the way, is this rule written > somewhere? If not, where would be a good place to write it? > And either way, it would be good to link to this as part of [2]. >=20 > Previous patches had to change the language for many structs, but "@see" = blocks > avoid the need to include those changes in this patchset. Rather than wa= ste > that work, I've temporarily moved those changes to the final patch in thi= s set. > My feelings about that last patch aren't strong, but I guess I'll propose= them > in a separate thread unless anyone wants them here or chucked altogether. >=20 >=20 > I've rewritten AVOptions and AVClass based on feedback. The new version > reflects a hypothetical that's been going round my head all week... >=20 > Imagine you wanted to write a system that nudged people to try new codecs. > It might say e.g. "you seem to be using H.264, would you like to try H.26= 5?" > Implementing that would probably involve a struct like: >=20 > struct AVOldNew { > AVClass* old; > AVClass* new; > }; AVClass would describe the internal decoder structures. This would not be correct at all in this example. Thats like handing a man 2 CAD documents about 2 engines of 2 cars If you wanted to suggest to get a tesla instead of a ford. One would have to describe the 2 cars and their differences thats 2 AVCodecDescriptor maybe thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB It is a danger to trust the dream we wish for rather than the science we have, -- Dr. Kenneth Brown --g3IWFuR7/O9KKcN6 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEKAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZk/ydgAKCRBhHseHBAsP q7QHAJ9CJpr81xssladc40ri0O+FwkcQgACghb1wbPG4o0LWTvZyZpiChryupsw= =brEN -----END PGP SIGNATURE----- --g3IWFuR7/O9KKcN6-- --===============5183310997425639244== 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". --===============5183310997425639244==--