Xref: utzoo comp.std.c:2622 comp.lang.c++:6839 gnu.g++:711 gnu.gcc:1450 comp.lang.c:26986
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!texbell!wuarchive!brutus.cs.uiuc.edu!uakari.primate.wisc.edu!ames!sgi!shinobu!odin!delrey!shap
From: shap@delrey.sgi.com (Jonathan Shapiro)
Newsgroups: comp.std.c,comp.lang.c++,gnu.g++,gnu.gcc,comp.lang.c
Subject: Re: #include "filename.h" does not mean "include user file"
Keywords: include
Message-ID: <5364@odin.SGI.COM>
Date: 16 Mar 90 21:57:55 GMT
References: <6928@cadillac.CAD.MCC.COM>
Sender: news@odin.SGI.COM
Followup-To: comp.std.c
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 18

In article <6928@cadillac.CAD.MCC.COM> ned@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