From: Greg Colvin (gcolvin_at_[hidden])
Date: 1999-07-28 20:03:13
From: Beman Dawes <beman_at_[hidden]>
> At 01:27 PM 7/28/99 -0600, Greg Colvin wrote:
>
> >> 2) #include <cstdint>,
> ...
> >I'm not sure that on all systems you can make this work -- you
> >may not be able to have a header without an extension, or you may
> >not be able to put your own stuff on the system path.
>
> Hum... This might be a problem in theory, but in practice are there
> really any compilers out there that would prevent (2)? Anyone know
> of a real-world compiler with either of these limitations?
I don't know about the real world (:-) but the standard seems to
say you should use the "name" form for including files.
16.2 Source file inclusion [cpp.include]
1 A #include directive shall identify a header or source file that can
be processed by the implementation.
2 A preprocessing directive of the form
# include <h-char-sequence> new-line
searches a sequence of implementation-defined places for a header
identified uniquely by the specified sequence between the < and >
delimiters, and causes the replacement of that directive by the entire
contents of the header. How the places are specified or the header
identified is implementation-defined.
3 A preprocessing directive of the form
# include "q-char-sequence" new-line
causes the replacement of that directive by the entire contents of the
source file identified by the specified sequence between the " delim-
iters. The named source file is searched for in an implementation-
defined manner. If this search is not supported, or if the search
fails, the directive is reprocessed as if it read
# include <h-char-sequence> new-line
with the identical contained sequence (including > characters, if any)
from the original directive.