From owner-acpi-jp@jp.freebsd.org  Thu Mar 22 10:58:51 2001
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id KAA34692;
	Thu, 22 Mar 2001 10:58:51 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from mass.dis.org ([206.112.127.152])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id KAA34677
	for <acpi-jp@jp.freebsd.org>; Thu, 22 Mar 2001 10:58:50 +0900 (JST)
	(envelope-from msmith@mass.dis.org)
Received: from mass.dis.org (localhost [127.0.0.1])
	by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2M1vcE01285
	for <acpi-jp@jp.freebsd.org>; Wed, 21 Mar 2001 17:57:39 -0800 (PST)
	(envelope-from msmith@mass.dis.org)
Message-Id: <200103220157.f2M1vcE01285@mass.dis.org>
X-Mailer: exmh version 2.1.1 10/15/1999
To: acpi-jp@jp.freebsd.org
In-reply-to: Your message of "Wed, 21 Mar 2001 17:47:34 PST."
             <4148FEAAD879D311AC5700A0C969E8905DE79C@orsmsx35.jf.intel.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 21 Mar 2001 17:57:38 -0800
From: Mike Smith <msmith@freebsd.org>
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 1117
Subject: [acpi-jp 1117] Re: acpica-unix-20010313.tar.gz 
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: msmith@freebsd.org

> > That's OK.  I assume you had a good reason for it.  You need 
> > to fix the 
> > include paths though, since you have inconsistent assumptions about 
> > include/platform (in some places you assume it's in the 
> > include path, in
> > others you explicitly refer to platform/foo.h).
> 
> Where were you seeing this? The only places that we should be referencing
> platform/foo.h as "foo.h" is from other headers in platform - we're assuming
> the current directory is in the search path. So, is that what you're talking
> about, do you view this as bad style, or are you referring to other places
> altogether?

The "current directory" for an include is the directory holding the 
source file, not the nested include.  So when you say 

#include "bar.h"

in a file you've included with

#include "platform/foo.h"

the search for bar.h is *not* going to look in the platform directory.

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E


