Subject: Re: multiple inclusion protection for kernel files
To: Izumi Tsutsui <tsutsui@ceres.dti.ne.jp>
From: Christos Zoulas <christos@zoulas.com>
List: tech-kern
Date: 12/04/2005 00:40:41
On Dec 4, 11:29am, tsutsui@ceres.dti.ne.jp (Izumi Tsutsui) wrote:
-- Subject: Re: multiple inclusion protection for kernel files

| In article <20051203215935.3D7C7564FA@rebar.astron.com>
| christos@zoulas.com wrote:
| 
| > 1. For files that get installed in /usr/include:
| >    All the code in the include file is bracketed by:
| > 
| >    #ifndef _[<DIR>_...]<FILENAME>_H_
| >    #define _[<DIR>_...]<FILENAME>_H_
| >    .... code ....
| >    #endif /* _[<DIR>_...]<FILENAME>_H_ */
| 
| Some files under include/machine/ use _MACHINE_FOO_H_
| but others use own ${MACHINE} names, like _HP300_FOO_H_.
| Which is better?

Since machine is a symlink, I would say that the real path is better.
So _HP300_FOO_H_.

christos