This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: #include_next fix for libio
On Mon, Apr 03, 2000 at 12:28:33PM -0700, Jason Merrill wrote:
> >>>>> Zack Weinberg <zack@wolery.cumb.org> writes:
>
> > On Sun, Apr 02, 2000 at 10:20:15PM -0700, Jason Merrill wrote:
> >> Why is this necessary? I missed the relevant cpp changes.
>
> > If -Wtraditional is on, #include_next will get a warning. The warning
> > is disabled in system headers, but when you're compiling libio, that
> > wrapper isn't considered a system header. (See the other thread on
> > this.)
>
> And adding an initial space defeats that?
Yes. The warning triggers if you have a directive known to K+R
compilers with an indented #, or a directive not known to K+R
compilers without an indented #. See
http://gcc.gnu.org/ml/gcc-patches/2000-02/msg00496.html for the
original suggestion.
zw