Date: Sat, 26 Sep 2015 18:37:29 -0000 From: Jonathan Anderson <jonathan@FreeBSD.org> To: Hans Petter Selasky <hps@selasky.org> Cc: Ed Schouten <ed@nuxi.nl>, Bruce Evans <brde@optusnet.com.au>, John-Mark Gurney <jmg@freebsd.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r286170 - head/share/man/man9 Message-ID: <6C371C1F-8758-4B31-A4D3-CF3D1A32DF9D@FreeBSD.org> In-Reply-To: <55C09869.2040605@selasky.org> References: <201508020022.t720MFqp023071@repo.freebsd.org> <20150802145434.V1128@besplex.bde.org> <CABh_MKm3cWbPu6WiP9i%2BF-6CuuAH-UAGcek8jEbN0ZxjNZ5GeA@mail.gmail.com> <55C09869.2040605@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Aug 4, 2015, at 8:18 AM, Hans Petter Selasky <hps@selasky.org> = wrote: >=20 > Wouldn't the argument be the same for queue.3 . Once C-compilers = finally decide to compile time support queues, we should throw queue.3 = aswell? Sure! Not right away, and not in a way that causes unnecessary churn, = but if there are benefits (e.g., better optimizations, better standards = compliance) and a diversity of compilers support a new C feature in both = our stable branches and the ports tree (for lots of architectures), then = why not? (note: by =E2=80=9Cdiversity=E2=80=9D, I don=E2=80=99t mean =E2=80=9CClang= and GCC support it on amd64 but none of the vendor toolchains for other = important architectures do=E2=80=9D) There are lots of things like this, where FreeBSD folk historically = said, =E2=80=9CK&R/C89/C99/C11 doesn=E2=80=99t provide feature X, so we = need to write some macros to do it ourselves.=E2=80=9D That=E2=80=99s = great, FreeBSD was ahead of its time, but once the C standard catches = up, isn=E2=80=99t it good to hew to the standard wherever it=E2=80=99s = practical to do so? stdatomic.h, _Generic, _Noreturn, static = assertions... the language is growing lots of useful features. = Wouldn=E2=80=99t it be good to adopt them when we can and trim = non-standard code? Cheers, Jon -- jonathan@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6C371C1F-8758-4B31-A4D3-CF3D1A32DF9D>