#import future (summary and proposed solutions)

[Neil Booth]

Timothy J. Wood wrote:-

> 
> On Saturday, January 25, 2003, at 09:57  PM, Zack Weinberg wrote:
> >Yes you are.  If this pattern doesn't work you're already hosed,
> >because you have a conflict on the short name of the file itself.
> 
>   But that's why the file name should not be used for the uniquing 
> (either in the include guards or by the #import machinery).  A 'good 
> enough' solution that uses the inode and some relatively persistent 
> filesystem identifier should give you five nines of reliability as 
> opposed to the five eights I've gotten with include guards :)

GCC has to work across NFS and non-Unix systems, so this is no good.

Neil.