This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [RFC] libstdc++/6720 and libstdc++/6671
- From: Zack Weinberg <zack at codesourcery dot com>
- To: Paolo Carlini <pcarlini at unitus dot it>
- Cc: Jonathan Wakely <cow at compsoc dot man dot ac dot uk>, libstdc++ at gcc dot gnu dot org
- Date: Wed, 22 May 2002 10:41:55 -0700
- Subject: Re: [RFC] libstdc++/6720 and libstdc++/6671
- References: <3CEBD5BA.10409@unitus.it>
On Wed, May 22, 2002 at 07:30:34PM +0200, Paolo Carlini wrote:
> >ext/algorithm includes <algorithm>
> >If this is changed to include "algorithm" will the preprocessor include
> >ext/algorithm from the current dir, or spot that that's the current file
> >and then proceed to look in the system dirs, finding the intended header?
>
> Sorry, now I get your point, but this could easily be solved by including
> "../algorithm", do you agree?
Yes to both -- #include "algorithm" will find the same file again
(sometimes people genuinely want to do that) and
#include "../algorithm" will do what you want.
zw