From: Devin Heitmueller <devin.heitmueller@ltnglobal.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 2/2] Require compilers to support C17. Date: Wed, 7 Feb 2024 11:15:30 -0500 Message-ID: <CAHGibzFKK-rNoqB_1OjgPWSpm_huW8tihH1jssHoC-e6BYGnhg@mail.gmail.com> (raw) In-Reply-To: <170729943020.8914.10821872629310998047@lain.khirnov.net> Hello Anton, On Wed, Feb 7, 2024 at 4:50 AM Anton Khirnov <anton@khirnov.net> wrote: > > Now I know that developers *LOVE* to use the latest whizbang language > > features, > > Could we please not have these kinds of caricatures in here? It's not > helpful. Permit me to rephrase: In my 25+ years of experience as a full-time C/C++ developer, I have run across many cases where a developer decided he/she/they wanted to use some relatively new language feature, often without consideration for the availability of compilers across popular platforms used by users. This is not the sort of thing that should be taken lightly, and usually needs discussion with the wider developer community (and in some cases the larger user community, depending on the project). In fact, that single developer often doesn't even have a complete picture of who is impacted by such a proposed change. Which is why we talk about it. Sometimes the answer is simply, "Hell no, we're not going to continue supporting Windows 98!". And sometimes the answer is, "Oh wait, that means these tens of thousands of users will need to upgrade their servers or cross-compile. Perhaps we shouldn't demand that of them just for the benefit of language feature X at this time..." > Not to mention anonymous unions were standardized in C11 and widely > available for many years (possibly decades) before that, so it's hardly > a 'latest whizbang feature'. Yeah, I said "anonymous unions" because that was actually the justification you offered for making C17 the minimum. I wasn't intending to offer a critique on using any specific language feature, but rather wanted to make sure everyone agreed on the implications of changing the minimum compiler version. > > but there's a reason that many projects choose to have > > relatively old minimum language versions. > > > > Now, again, if the developer community all agree that it makes sense > > to stop supporting an operating system that was shipping as recently > > as five years ago, then so be it. But this sort of deprecation > > shouldn't simply be the result of a single developer deciding he wants > > to use anonymous unions (or some other C17 feature) and thus we drop > > support for a bunch of operating system versions. > > In case you missed it, I didn't just randomly send this out of the blue, > it was discussed at the FOSDEM dev meeting (and before that on IRC and > the ML) and literally nobody in the room was against moving to C11. Right, so like many people I'm not on the IRC 24x7, and regrettably I couldn't make the FOSDEM meeting. Perhaps I simply overlooked it, but I couldn't find anything on the ML other than the patch you sent on February 3rd changing it to C11. Given the possible implications, I would have expected to see a discussion on the ML. If such a discussion did happen on the ML and I overlooked it, then I guess it's on me for not raising concerns earlier. In fact, the FOSDEM discussion and the earlier patch was about C11, which I actually don't have any objection to. I would argue the same discussion should be had to assess the impact and conclude whether it's worth it, but it doesn't effect any of my use cases and (in my opinion) there are likely to be far fewer users impacted by such a change. This feels like just the sort of thing the TC is meant to discuss/resolve. And the fact that your position as the developer submitting the patch is that it's "no big deal" is exactly why it's the sort of thing that needs agreement from a wider audience. Devin -- Devin Heitmueller, Senior Software Engineer LTN Global Communications o: +1 (301) 363-1001 w: https://ltnglobal.com e: devin.heitmueller@ltnglobal.com _______________________________________________ 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:[~2024-02-07 16:15 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-05 19:54 [FFmpeg-devel] [PATCH 1/2] lavc/refstruct: do not use max_align_t on MSVC Anton Khirnov 2024-02-05 19:54 ` [FFmpeg-devel] [PATCH 2/2] Require compilers to support C17 Anton Khirnov 2024-02-05 20:12 ` James Almer 2024-02-05 20:13 ` Anton Khirnov 2024-02-05 20:13 ` Devin Heitmueller 2024-02-05 20:30 ` Anton Khirnov 2024-02-05 20:33 ` James Almer 2024-02-05 20:40 ` Devin Heitmueller 2024-02-07 9:50 ` Anton Khirnov 2024-02-07 16:15 ` Devin Heitmueller [this message] 2024-02-07 16:36 ` Anton Khirnov 2024-02-05 20:53 ` Niklas Haas 2024-02-09 11:22 ` Dominik 'Rathann' Mierzejewski 2024-02-09 12:04 ` Kevin Wheatley 2024-02-05 20:20 ` Lynne 2024-02-05 20:27 ` Michael Niedermayer 2024-02-05 20:31 ` Anton Khirnov 2024-02-05 20:45 ` Michael Niedermayer 2024-02-07 9:55 ` Anton Khirnov [not found] ` <2E73439B-3AE5-46FC-80FB-2D375FD852C5@cosmin.at> 2024-02-07 18:52 ` Cosmin Stejerean via ffmpeg-devel 2024-02-07 19:27 ` Lynne [not found] ` <1CBFE199-B1ED-47B5-BD97-7DA715EAB55B@cosmin.at> 2024-02-07 21:10 ` Cosmin Stejerean via ffmpeg-devel 2024-02-07 21:19 ` James Almer 2024-02-08 7:15 ` Rémi Denis-Courmont 2024-02-08 10:42 ` Andreas Rheinhardt 2024-02-07 21:48 ` Lynne [not found] ` <8C790A7E-A236-4413-A4EB-AFE2F91E96A8@cosmin.at> 2024-02-08 0:36 ` Cosmin Stejerean via ffmpeg-devel 2024-02-08 4:29 ` Jean-Baptiste Kempf 2024-02-08 18:52 ` Sean McGovern 2024-02-08 19:05 ` James Almer 2024-02-08 19:46 ` Lynne 2024-02-05 20:55 ` Niklas Haas 2024-02-05 22:22 ` Stefano Sabatini 2024-02-07 9:53 ` Anton Khirnov 2024-02-06 6:50 ` Diederick C. Niehorster 2024-02-06 12:03 ` Lynne
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=CAHGibzFKK-rNoqB_1OjgPWSpm_huW8tihH1jssHoC-e6BYGnhg@mail.gmail.com \ --to=devin.heitmueller@ltnglobal.com \ --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