nagle@animats.com (John Nagle) wrote in message news:<273gc.37698$tj4.2001@newssvr29.news.prodigy.com>...
> Matthew Collett wrote:
>
> > In article <3cIfc.51826$75.2848@newssvr25.news.prodigy.com>,
> >  nagle@animats.com (John Nagle) wrote:
> >
> >
> >> Perl searches entire subtrees for
> >>included files; the C++ preprocessor does not.
> >
> >
> > I hadve always understood the way the preprocessor searches for includes
> > to be entirely implementation defined...
>
>    Does that mean that this issue should be referred to the
> IEEE's Portable Application Standards Committee, for incorporation
> into the POSIX standard?  If the C++ committee explicitly takes the position
> that the syntax and semantics of what appears within the quote marks of "include"
> lies outside their scope, the issue properly belongs to PASC.

The standard specifies a large portion of implementation-defined
behavior for header names, without leaving it completely unspecified:

1. "How the places are specified or the header identified is
implementation-defined."
2. "the named source file is searched for in an implementation-define
manner."
3. "The method by which a sequence of preprocessing tokens between a <
and a > processing token pair o a pair of " characters is combined
into a single header name processin token is implementation-defined.
4. "The mapping between the delimited sequence and the external source
file name is implemenation-defined."
5. There is an "implementation-defined nesting limit" for #includes.

---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html                       ]