Can't find includes to silence warnings

[Joe Esch" <joe at sketchup.com (Joe Esch)]

OTOH, if you always just use #import in your Objective-C code, you know that
it will work and do not have to worry about what the contents of the
included files are.  It seems to me that this would out weight the
possibility of some slight performance penalty during compilation.

>
> On Sunday, March 3, 2002, at 10:40  AM, Kim Foo-Jones wrote:
>
> > On Saturday, March 2, 2002, at 09:43 , Matt Watson wrote:
> >
> >> On Saturday, March 2, 2002, at 01:15  PM, Finlay Dobbie wrote:
> >>
> >>> #include <unistd.h> (or #import if you're using Obj-C).
> >>
> >> Don't #import <unistd.h> -- it already has multiple-include protection:
> >>
> >> #ifndef _UNISTD_H_
> >> #define _UNISTD_H_
> >
> > Why is it necessary to avoid #import in this case?
>
> It's not necessary to avoid it, it's just not as efficient to use it,
> since the multiple-include issue is already taken care of in the header
> directly, so using #import is redundant.
>
> matt.
>
> _______________________________________________
> MacOSX-dev mailing list
> MacOSX-dev@xxxxxxxxxxxxx
> http://www.omnigroup.com/mailman/listinfo/macosx-dev
>
>