Date: Thu, 7 Mar 2013 22:07:59 -0500 From: Eitan Adler <lists@eitanadler.com> To: Tijl Coosemans <tijl@coosemans.org> Cc: freebsd-toolchain@freebsd.org Subject: Re: c89 broken on head? Message-ID: <CAF6rxg=TdfXkkDd7CCnQdo0qEb7kLjh0YLiwnZgb6VL5Q_uCzQ@mail.gmail.com> In-Reply-To: <51391CC1.5050200@coosemans.org> References: <5138CD6B.2050309@coosemans.org> <5138EA4C.1060001@FreeBSD.org> <5138F6EF.6020203@coosemans.org> <51390682.3020703@FreeBSD.org> <48120A0D-8A96-4D62-9C17-AE40E1DEF026@bsdimp.com> <51391CC1.5050200@coosemans.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7 March 2013 18:03, Tijl Coosemans <tijl@coosemans.org> wrote: > On 2013-03-07 22:36, Warner Losh wrote: >> On Mar 7, 2013, at 2:28 PM, Dimitry Andric wrote: >>> On 2013-03-07 21:22, Tijl Coosemans wrote: >>> ... >>>> Because it's the practical thing to do? Old code/makefiles can't possibly >>>> be expected to know about compilers of the future, while new code can be >>>> expected to add -std=c11. >>> >>> I am not sure I buy that argument; if it were so, we should default to >>> K&R C instead, since "old code" (for some arbitrary definition of "old") >>> could never have been expected to know about gcc defaulting to gnu89. > > My argument was to be practical, i.e. don't change what doesn't have to > change. > >> -std=c11 is defintely too new, but maybe c89 is too old. >> >> I thought the c89 program actually was mandated by POSIX, no? > > Both were part of POSIX. c89 was a strict ISO c89 compiler, while cc was > c89, but could additionally accept "an unspecified dialect of the C > language". http://pubs.opengroup.org/onlinepubs/007908799/xcu/cc.html > > So, if practicality isn't a good enough argument, maybe POSIX compliance > is? cc is marked as "LEGACY" which is described as optional ("need not be provided"). However, I would not be surprised if a non-zero number of ports depend on cc existing. If we are to remove it or change it, I would like to see that preceded by an exp-run. -- Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxg=TdfXkkDd7CCnQdo0qEb7kLjh0YLiwnZgb6VL5Q_uCzQ>