First of all: thank you. You solved my problem.
There's no real way to enforce privateness, either in Objective-C
or C++.
Why not in C++?
Yes, these do the trick.
But another->mineAlone will.
-(int)yoursTooButWithAnother: (PrivateClass *)another {
return another->mineAlone % 3;
}
Also, be careful to keep two things separate in your mind.
-- The *variable* mineAlone, which can be referenced in the class's
methods as 'mineAlone' or 'self->mineAlone'.
-- The *property* mineAlone, which can be referenced in the class's
methods as '[self mineAlone]' or 'self.mineAlone'.
They only "accidentally" have the same name.
Yes.
Cheers Horst
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
