From -1743638872865917999
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f78e5,6949d6499f54708
X-Google-Attributes: gidf78e5,public
From: scherrey@proteus-tech.com
Subject: Re: Stupid Preprocessor Question
Date: 1995/04/30
Message-ID: <3numgb$cdo@keystone.intergate.net>#1/1
X-Deja-AN: 101764451
references: <41d7cb$03325.3a@rd.surface.com>
organization: Proteus Technologies, Inc.
reply-to: scherrey@proteus-tech.com
newsgroups: comp.std.c++

In <41d7cb$03325.3a@rd.surface.com>, mbw@surface () writes:
>  If I have two header files, a.h and b.h, and they are both
>in ../../Common/ (relative to my .C or .cpp file), and I want to include
>b.h from a.h, should a.h say
>  #include "b.h"
>or should it say
>  #include "../../Common/b.h"
>?
>
> Borland 4.02 seems to require the latter, which seems insane, while 
>MS 2.1a likes the former, which seems correct to me.  But my
>code has to compile under both and I just wish they agreed.

    Borland has no such requirement as long as you specify include path options.