Re: #include_next: wrong search order?

[Alexey Neyman <alex dot neyman at auriga dot ru>]

I believe this is a bug in the preprocessor (though longstanding one - 
I checked even egcs 2.91 and it appeared there as well). For details, 
refer to http://gcc.gnu.org/ml/gcc-patches/2005-03/msg00736.html

On Friday 04 March 2005 19:42, corey taylor wrote:
> Eljay, Alexey,
> 
>   So the order isn't influenced at all by previous includes?
> 
> corey
> 
> 
> On Fri, 04 Mar 2005 10:35:23 -0600, Eljay Love-Jensen 
<eljay@adobe.com> wrote:
> > Hi Alexey,
> > 
> > You are right, I was mistaken.  I stand corrected.
> > 
> > The #include_next does start with the next system include 
directory on the
> > system include path (not include the current one or the prior 
ones).
> > 
> > Sincerely,
> > --Eljay
> > 
> >
> 

-- 
Let us help you.  Let us heal you. Let us love you.
                        -- Pkunks, SC2