This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: Why warn about #include_next in system headers?

To: Zack Weinberg <zackw at Stanford dot EDU>
Subject: Re: Why warn about #include_next in system headers?
From: Neil Booth <neil at daikokuya dot demon dot co dot uk>
Date: Tue, 6 Feb 2001 19:37:49 +0000
Cc: gcc-bugs at gcc dot gnu dot org
References: <01020523112001.26861@enzo.bigblue.local> <20010205231508.C3104@daikokuya.demon.co.uk> <01020600221104.26861@enzo.bigblue.local> <orpugw376m.fsf@guarana.lsd.ic.unicamp.br> <20010206082340.H3104@daikokuya.demon.co.uk> <20010206003503.A525@wolery.stanford.edu> <20010206185407.I3104@daikokuya.demon.co.uk> <20010206112418.E525@wolery.stanford.edu>

Zack Weinberg wrote:-

[Good ideas for improvements...]

> Possibly this can be done in conjunction with Neil's proposed driver
> rewrite.

All that sounds like a good idea.  I've not yet really got started on
it, but I've thought about some of the issues a bit.

After we branch or release, I'll start taking it seriously.

Neil.

References:
- Why warn about #include_next in system headers?
  - From: Franz Sirl
- Re: Why warn about #include_next in system headers?
  - From: Neil Booth
- Re: Why warn about #include_next in system headers?
  - From: Franz Sirl
- Re: Why warn about #include_next in system headers?
  - From: Alexandre Oliva
- Re: Why warn about #include_next in system headers?
  - From: Neil Booth
- Re: Why warn about #include_next in system headers?
  - From: Zack Weinberg
- Re: Why warn about #include_next in system headers?
  - From: Neil Booth
- Re: Why warn about #include_next in system headers?
  - From: Zack Weinberg

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]