|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
Thank you for your detailed explanation.
Well... isn't it be controlled by @private, @protected, and @public?
No. @private, @protected, and @public apply only to instance variables and not instance methods. As a practical matter, @private, @protected, and @public cannot be enforced even for instance variables at run-time because an instance can always be treated as a C struct via @defs(class_name) and the variables can be accessed using simple C structure dereference.
If things are omitted in interface files and they are written in their implementation files, it would be easy to lose track, and although some methods are deleted accidently from the implementation file, it would be easier to figure out which one is omitted or not.
By default, an Objective-C compiler will WARN you that a method is declared but not implemented. Implementing a method that is not declared is not even worth a warning. It is normal.
So, this is the reason behind my question.
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=++=+=+=+= JongAm Park Home : http://my.dreamwiz.com/jongam Blog : http://jongampark.blogspot.com Tel)213-251-9592 MSN : email@hidden H.P)213-820-8943 AIM/iChat : JongAm _______________________________________________ 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
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.