This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: #import future (summary and proposed solutions)
- From: Nicola Pero <nicola at brainstorm dot co dot uk>
- To: Paul Schlie <schlie at attbi dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 27 Jan 2003 02:05:01 +0000 (GMT)
- Subject: Re: #import future (summary and proposed solutions)
> All that should be necessary to support the intent of #import, is to
> reasonably inhibit the inclusion of a uniquely named file multiple times,
> under reasonably typical conditions (i.e. inhibit the multiple inclusion
> of files which resolve to the same absolute path and name, where it's the
> responsibility of the author of the build environment to establish such
> conditions, if #import is desired to behave as expected).
I guess your `reasonably typical conditions' would be something like `all
headers must be on the same linux filesystem, and you must not be using
anything "complex" [such as links], else GCC won't be guaranteed to be
able to compile your (correct) ObjC source code' ?
It doesn't sound like a serious option.