This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: #include_next: wrong search order?
- From: Eljay Love-Jensen <eljay at adobe dot com>
- To: Alexey Neyman <alex dot neyman at auriga dot ru>, gcc-help at gcc dot gnu dot org
- Date: Fri, 04 Mar 2005 06:32:01 -0600
- Subject: Re: #include_next: wrong search order?
- References: <200503041455.49130.alex.neyman@auriga.ru>
Hi Alexey,
>Therefore, it appears that the lines [5] and [6] are wrong:
It doesn't appear wrong to me.
When a #include is done (or the GCC
behind-the-covers-don't-use-this-in-your-code #include_next), it pulls in
the specified file as if embedded, then returns back to processing the
first file. That's what I see in your y.c result.
FYI - you can see your system include path via "gcc -E -v y.c".
HTH,
--Eljay