Re: Warnings that won't go away
Re: Warnings that won't go away
- Subject: Re: Warnings that won't go away
- From: Daniel Jalkut <email@hidden>
- Date: Wed, 30 Nov 2005 21:02:13 -0500
Well, I guess it's 'a good thing we're not working on the same
project :)
I can actually see both approaches as very reasonable. I suppose
it's mostly a matter of habit. I am almost even convinced by your
data hiding argument to try to change my ways.
I guess I would probably come all the way over to your side if the
headers involved were public headers. It especially seems best to
inflict as little as possible on a client who isn't entitled to
change the header on their own. Perhaps that alone is a good enough
argument to always follow your advice.
We'll see what I'm doing in a year's time!
Daniel
On Nov 30, 2005, at 11:07 AM, j o a r wrote:
I think that it's more interesting to focus on the conceptual
benefits of reducing dependencies via data hiding, than to think
about how it will affect performance.
But regardless, my recommendation would actually be almost reversed:
1) Only #import what you have to, and
2) If you're in a header file, never use #import when you can use
@class
_______________________________________________
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