This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: #include_next fix for libio
>>>>> 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?
Jason