Date: Tue, 26 Jul 2022 10:31:17 -0600 From: Warner Losh <imp@bsdimp.com> To: "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Stlye(9) strengthen statements on not using K&R function definitions Message-ID: <CANCZdfqgjM52fVoCbEo0PteW7%2BGz5L0CJ=yBZ%2BKshVUY7Utx1A@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
--000000000000d730a705e4b7d32b Content-Type: text/plain; charset="UTF-8" Greetings I've posted a review https://reviews.freebsd.org/D35945 which strengths statements about K&R definitions and declarations: don't use them. Most of the K&R code has been removed from the tree (ufs being the last straggler). Future versions of the C standard will remove the K&R definitions and declaration syntax. clang 15 will whine about this construct. The time is ripe to move to language that suggests an outright prohibition. Comments about language? Make them in phabricator. Comments about the idea? Reply here Warner --000000000000d730a705e4b7d32b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Greetings</div><div><br></div><div>I've posted a = review <a href=3D"https://reviews.freebsd.org/D35945">https://reviews.freeb= sd.org/D35945</a> which strengths statements about K&R definitions and = declarations: don't use them. Most of the K&R code has been removed= from the tree (ufs being the last straggler). Future versions of the C sta= ndard will remove the K&R definitions and declaration syntax. clang 15 = will whine about this construct.</div><div><br></div><div>The time is ripe = to move to language that suggests an outright prohibition.</div><div><br></= div><div>Comments about language? Make them in phabricator.</div><div>Comme= nts about the idea? Reply here<br></div><div><br></div><div>Warner</div><di= v><br></div></div> --000000000000d730a705e4b7d32b--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqgjM52fVoCbEo0PteW7%2BGz5L0CJ=yBZ%2BKshVUY7Utx1A>