bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnulib] K&R C or ANSI C89 ?


From: Jeff Bailey
Subject: Re: [Bug-gnulib] K&R C or ANSI C89 ?
Date: Tue, 12 Nov 2002 12:06:15 -0800
User-agent: Mutt/1.3.28i

On Tue, Nov 12, 2002 at 11:39:04AM -0800, Paul Eggert wrote:

> > - What other K&R C compatibility requirements, except for GCC, exist?

> Since even Sun is dropping support for SunOS 4, I think it's quite all
> right if the GNU project does too.

The GCC Steering Committee's decsision to allow ISO C (89) in
non-bootstrap portions of the compiler:

http://gcc.gnu.org/ml/gcc/2002-06/msg00871.html

and http://gcc.gnu.org/ml/gcc/2002-06/msg01714.html

contains the note:

OTOH, my personal opinion is let's be practical.  If you submit a patch
to a freebsd specific file with a string concatenation in it, no one
will probably care (as long as you're happy living with the extra
warning.) E.g. the solaris2 port uses string concatenation in the specs
stuff and no one minds.  I just live with the extra warning when I
bootstrap there.

http://www.gnu.org/prep/standards_10.html#SEC10 says:

1989 Standard C is widespread enough now that it is ok to use its
features in new programs. There is one exception: do not ever use the
"trigraph" feature of Standard C.

1999 Standard C is not widespread yet, so please do not require its
features in programs. It is ok to use its features if they are present. 

I don't remember if bison and flex are required when building GCC, or
are just required when building the release tarball.  If it's just when
building the release tarball, then I think we're fine to completely drop
K&R C - the toolchain will continue to use libiberty for the predictable
future.

Tks,
Jeff Bailey





reply via email to

[Prev in Thread] Current Thread [Next in Thread]