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 69AC540C42 for ; Sat, 2 Sep 2023 20:03:42 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 20F5168C74A; Sat, 2 Sep 2023 23:03:40 +0300 (EEST) Received: from relay9-d.mail.gandi.net (relay9-d.mail.gandi.net [217.70.183.199]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 1762568C39A for ; Sat, 2 Sep 2023 23:03:34 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id 1C5CAFF804 for ; Sat, 2 Sep 2023 20:03:32 +0000 (UTC) Date: Sat, 2 Sep 2023 22:03:32 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20230902200332.GA8640@pb2> References: <20230826180748.15977-1-anton@khirnov.net> <169329808575.20400.4593289958410673620@lain.khirnov.net> <2693951.mvXUDI8C0e@basile.remlab.net> MIME-Version: 1.0 In-Reply-To: <2693951.mvXUDI8C0e@basile.remlab.net> X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] [PATCH 4/6] doc/developer: add a code behaviour section to development policy 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="===============2756294544797835267==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============2756294544797835267== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="yrj/dFKFPuw6o+aM" Content-Disposition: inline --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 01, 2023 at 08:10:11PM +0300, R=E9mi Denis-Courmont wrote: > Le torstaina 31. elokuuta 2023, 18.28.48 EEST Stefano Sabatini a =E9crit : > > On date Tuesday 2023-08-29 10:34:45 +0200, Anton Khirnov wrote: > > > Quoting Stefano Sabatini (2023-08-27 14:38:44) > > >=20 > > > > Il sab 26 ago 2023, 20:08 Anton Khirnov ha scri= tto: > > > > > Document our longstanding de facto policies on things like > > > > > correctness, > > > > > thread-safety, UB, etc. > > > >=20 > > > > UB? > > >=20 > > > undefined behavior > >=20 > > yes, let's avoid acronyms >=20 > I think that developers should know common accronyms of the primary=20 > programming language of the project, and it is totally reasonable to expe= ct=20 > that they are. >=20 > And yes, UB is a very well known accronym in this context. In my experien= ce,=20 > people who don't know the accronym don't know the concept either, so spel= ling=20 > it out wouldn't even help. There is a difference between not knowing a concept and not knowing what concept is referenced. "Undefined behavior" can be googled, and can to some extend be understood =66rom the meaning of the words by people with a math background. googling "UB" results in "Universit=E4tsbibliothek Wien" here and nothing on the first page of links is related to "undefined" So i do think, in case of a policy or some coding rules it should be spelle= d out thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB The bravest are surely those who have the clearest vision of what is before them, glory and danger alike, and yet notwithstanding go out to meet it. -- Thucydides --yrj/dFKFPuw6o+aM Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZPOVEAAKCRBhHseHBAsP q4nUAJ0Q+838JaxAfz53EZks5es1arz1wQCeOT89An90DIXb0k7bQdHKtnzyp9A= =3iQ0 -----END PGP SIGNATURE----- --yrj/dFKFPuw6o+aM-- --===============2756294544797835267== 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". --===============2756294544797835267==--