Re: #import future (summary and proposed solutions)

["Gareth Pearce" <tilps at hotmail dot com>]

> [...]
> >    How do oponents of #import think we are supposed to write header
> > guards??  Are we supposed to use this silly pattern?
> >
> > #ifndef _FILENAME_H
> > #define _FILENAME_H
> > ...
> > #endif /* _FILENAME_H*/
> >
> >    What happens when you get two competing packages with the same
> > file?
>
> 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.

What about ... when your working on a project with local copies of 2
libraries since you dont want to rely on the version of the system
libraries.  Both of which use the above pattern for all their headerguards.
#include "lib1/filename.h"
#include "lib2/filename.h"
would not be rediculous right?

Gareth