Re: Warnings that won't go away
Re: Warnings that won't go away
- Subject: Re: Warnings that won't go away
- From: Alastair Houghton <email@hidden>
- Date: Wed, 30 Nov 2005 18:37:18 +0000
On 30 Nov 2005, at 17:23, Dan Messing wrote:
Personally, I wouldn't recommend adding any more #imports you
actually have to to the header file I think that will just add more
confusion to the problem that you started with, even if it does get
rid of some warnings.
Although, on a cautionary note, you do need to make sure that your
header files will actually work without lots of additional #imports
in your source files. It's quite easy to go much to far the other
way and end up with a set of headers that will only work if you
include/import them in the right order; I've seen the results of this
first-hand, and it isn't pretty.
For instance, if your header depends on a system header, and won't
work without it included, it's best to #import/#include it in the
header file rather than requiring every source file that imports your
header to also include/import the other header.
Kind regards,
Alastair.
--
http://www.alastairs-place.net
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden