[bind10-dev] coding guidelines

[JINMEI Tatuya / 神明達哉]

At Wed, 17 Oct 2012 08:06:39 +0000,
Francis Dupont <fdupont at isc.org> wrote:

> => From N1570 (the last C11 draft):
> 
> 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 "
>   delimiters. 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.
> 
> I didn't look at the C++11 spec but there is no reason for C++ to be
> different on this point. (PS: just checked: the text is the same, i.e.,
> implementation-defined).

So, is your concern that since how <> or "" works is
implementation-defined, we cannot reliably assume anything anyway, in
theory?

---
JINMEI, Tatuya