Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!aplcen!uakari.primate.wisc.edu!brutus.cs.uiuc.edu!wuarchive!udel!princeton!idacrd!desj
From: desj@idacrd.UUCP (David desJardins)
Newsgroups: comp.lang.c
Subject: Re: Why don't nested #include's start at the source directory?
Message-ID: <527@idacrd.UUCP>
Date: 12 Dec 89 17:48:53 GMT
References: <49549@bbn.COM>
Organization: idacrd, princeton, nj
Lines: 14

From article <49549@bbn.COM>, by jgrace@bbn.com (Joe Grace):
> I have found a surprising, annoying and disappointing "feature" of
> both /lib/cpp (SunOS3.5) and GNU cpp:
> 
>   ./bar/1.h:
>   #include "2.h"

   The behavior looks perfectly correct to me.  The meaning of the
file 1.h should not depend on where you compile it from.  Looking at
the file by itself, obviously the place to look for 2.h is in the
directory where 1.h is found.  If you want it to find 2.h in the ..
directory, then write #include "../2.h".

   -- David desJardins