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 003B645CDA for ; Wed, 3 May 2023 17:52:54 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 552DE68BF1C; Wed, 3 May 2023 20:52:50 +0300 (EEST) Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id B408168BEFE for ; Wed, 3 May 2023 20:52:44 +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 343HqhcW006264 for ; Wed, 3 May 2023 19:52:44 +0200 Received: by phare.normalesup.org (Postfix, from userid 1001) id DF5C0EB5BF; Wed, 3 May 2023 19:52:43 +0200 (CEST) Date: Wed, 3 May 2023 19:52:43 +0200 From: Nicolas George To: FFmpeg development discussions and patches Message-ID: References: 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]); Wed, 03 May 2023 19:52:44 +0200 (CEST) Subject: Re: [FFmpeg-devel] Embedded documentation? 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="===============5815596157656182052==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============5815596157656182052== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="xGH/AE8jeI4e8csr" Content-Disposition: inline --xGH/AE8jeI4e8csr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Diederick C. Niehorster (12023-05-01): > +1. Thanks. > I assume a lot of the AVDocNode can be automatically populated from i= ts > corresponding option? We'd not want to maintain, e.g. option names and > aliases in more than one place. I cannot promise there will be no duplication at all, and AVOption is very limited and needs to be replaced anyway. But I can promise it will not have to be written as a C structure with all its fields initialized. I have not discussed it nor finalized any of the details, but I am thinking the build system will parse either doxy-style comments in the C source code or in a separate .md file with the same name to generate the structures for the built-in documentation. If the system parses comments in the C source, it can also parse the AVOption initializers, at least in the simple cases. Regards, --=20 Nicolas George --xGH/AE8jeI4e8csr Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE6ooRQGBoNzw0KnwPcZVLI8pNxgwFAmRSn2kACgkQcZVLI8pN xgzRgRAAuTqnLFETj+Owqp2rhszDQdq7W0v+yZgMssjQo0xkHaEjJa4Nxsu1jchV vYJHM7IMlRfq/A79iIrm728h89LI2lFoAF3OBXmcwOXVUghGnb6Uonqoevh1Fg/m 1CQC9RDRRsDdgdOn8NbGdzdT3j7R3kY9AwrPIODUuiUBOwF6+2ftgYzShy3mQqif d9twJG8EDZUoLbkR3Jf02x4ihbxGmQqwDkDkmJZt3Q5MbCpCx5UkrJsFy4Xmy4U1 PZJfKB2zIQ2ADV9yai3zTNcB0bPCUcS/oSpvz/HyijSrUAUGKjA1dnlNRX3k87JM S4U/Rs7tuqmYxZM2DGeuNy7lfM48jI3oBlqLoldggZ8o1ciVl8/m6zIENYHSl/hG rv+pUMZEerrHM6vADAFzD+HY1CPmCLu5FaY8v/P2HQN/m3UVNzJrIsc/M6FTOjDG vPgSwrieQ5+38mTHR3+v6O1eE2MQwnkpJuu0AEH8TPVAuyqw9So+1/fZUfJtCNo9 44wcqauslcKS3lgo7LkEs4v1nv69A+2/UUtW829/sddaJXzJ/xk3TXu+RF7tGxPm 3mQBftotNPpem+cFHRWa8iib2rOH6boUgoJQXn1lNcSLtX3Gq1i2cFEpuvuMzOgd LXYvFu+uhH6YLXcWH0WbsOhpJwQR4Pko9AEHDdXOmyYPIXS2kHo= =Xq2y -----END PGP SIGNATURE----- --xGH/AE8jeI4e8csr-- --===============5815596157656182052== 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". --===============5815596157656182052==--