#include "filename.h" does not mean "include user file"

Jonathan Shapiro shap at delrey.sgi.com
Sat Mar 17 07:57:55 AEST 1990


In article <6928 at cadillac.CAD.MCC.COM> ned at MCC.COM (Ned Nowotny) writes:
>[ Note:  Followups are directed to comp.std.c.  GNU mailing list readers ]
>[        should probably just take note.                                 ]
>
[ Discussion of meaning of #include "file" ellided... ]

To preclude the rash of corrections, the issue is well known.  Early
cpp specs didn't specify whether the "file" syntax meant relative to
the file that did the include or relative to the source file.  The cpp
by Jon Reiser (sp?) implemented the former, when the latter was the
intended meaning.

Reiser's preprocessor has spread and a few very strange folks have
come to depend on the behavior.

In any case, it is well understood.

Jon



More information about the Comp.lang.c mailing list