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: Mon, 5 Feb 2024 15:40:43 -0500
Message-ID: <CAHGibzGn59O+nXZ0h84v+GBTvf6+Smi1dg3veP4=pKh=L3RFsA@mail.gmail.com> (raw)
In-Reply-To: <170716505807.8914.4209601292651825753@lain.khirnov.net>
On Mon, Feb 5, 2024 at 3:31 PM Anton Khirnov <anton@khirnov.net> wrote:
>
> Quoting Devin Heitmueller (2024-02-05 21:13:22)
> > On Mon, Feb 5, 2024 at 2:59 PM Anton Khirnov <anton@khirnov.net> wrote:
> > >
> > > It should be available in all relevant modern compilers and will allow
> > > us to use features like anonymous unions.
> >
> > Is everybody on board with the implications for this patch in terms of
> > platforms we allow building on? For example, the gcc on Centos7
> > doesn't support C17, and that isn't *that* old of a platform.
>
> According to Wikipedia, it's almost 10 years old. That counts as *that*
> old in my book. If someone really needs current ffmpeg on such a
> platform, they can still build their own compiler or cross-compile.
Another way to look at it is that it's what all Centos users used
until Centos8 was shipped in September 2019 (i.e. less than five years
ago).
Now I know that developers *LOVE* to use the latest whizbang language
features, 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.
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-05 20:41 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 [this message]
2024-02-07 9:50 ` Anton Khirnov
2024-02-07 16:15 ` Devin Heitmueller
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='CAHGibzGn59O+nXZ0h84v+GBTvf6+Smi1dg3veP4=pKh=L3RFsA@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