From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 4/6] doc/developer: add a code behaviour section to development policy Date: Sat, 2 Sep 2023 22:03:32 +0200 Message-ID: <20230902200332.GA8640@pb2> (raw) In-Reply-To: <2693951.mvXUDI8C0e@basile.remlab.net> [-- Attachment #1.1: Type: text/plain, Size: 1673 bytes --] On Fri, Sep 01, 2023 at 08:10:11PM +0300, Rémi Denis-Courmont wrote: > Le torstaina 31. elokuuta 2023, 18.28.48 EEST Stefano Sabatini a écrit : > > On date Tuesday 2023-08-29 10:34:45 +0200, Anton Khirnov wrote: > > > Quoting Stefano Sabatini (2023-08-27 14:38:44) > > > > > > > Il sab 26 ago 2023, 20:08 Anton Khirnov <anton@khirnov.net> ha scritto: > > > > > Document our longstanding de facto policies on things like > > > > > correctness, > > > > > thread-safety, UB, etc. > > > > > > > > UB? > > > > > > undefined behavior > > > > yes, let's avoid acronyms > > I think that developers should know common accronyms of the primary > programming language of the project, and it is totally reasonable to expect > that they are. > > And yes, UB is a very well known accronym in this context. In my experience, > people who don't know the accronym don't know the concept either, so spelling > 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 from the meaning of the words by people with a math background. googling "UB" results in "Universitätsbibliothek 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 spelled out thx [...] -- 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 [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 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".
next prev parent reply other threads:[~2023-09-02 20:03 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-26 18:07 [FFmpeg-devel] [PATCH 1/6] doc/developer: move a sentence to a more appropriate place Anton Khirnov 2023-08-26 18:07 ` [FFmpeg-devel] [PATCH 2/6] doc/developer: merge the 'contributing code' section into its parent chapter Anton Khirnov 2023-08-27 12:19 ` Stefano Sabatini 2023-08-26 18:07 ` [FFmpeg-devel] [PATCH 3/6] doc/developer: fix a nonsense statement Anton Khirnov 2023-08-27 12:21 ` Stefano Sabatini 2023-08-26 18:07 ` [FFmpeg-devel] [PATCH 4/6] doc/developer: add a code behaviour section to development policy Anton Khirnov 2023-08-26 18:36 ` Andreas Rheinhardt 2023-08-26 18:54 ` Anton Khirnov 2023-08-27 12:38 ` Stefano Sabatini 2023-08-29 8:34 ` Anton Khirnov 2023-08-31 15:28 ` Stefano Sabatini 2023-09-01 17:01 ` Michael Niedermayer 2023-09-01 17:10 ` Rémi Denis-Courmont 2023-09-01 17:26 ` Paul B Mahol 2023-09-01 18:33 ` Stefano Sabatini 2023-09-02 20:03 ` Michael Niedermayer [this message] 2023-09-03 8:29 ` Rémi Denis-Courmont 2023-09-03 16:21 ` Michael Niedermayer 2023-08-26 18:07 ` [FFmpeg-devel] [PATCH 5/6] doc/developer: drop an outdated item Anton Khirnov 2023-08-27 12:40 ` Stefano Sabatini 2023-08-26 18:07 ` [FFmpeg-devel] [PATCH 6/6] doc/developer: deduplicate commit message rules Anton Khirnov 2023-08-27 12:46 ` Stefano Sabatini 2023-08-27 12:18 ` [FFmpeg-devel] [PATCH 1/6] doc/developer: move a sentence to a more appropriate place Stefano Sabatini
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20230902200332.GA8640@pb2 \ --to=michael@niedermayer.cc \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git