Sorry for the inaccuracy.
I am well aware that there is no such thing as a true private method
in Objective-C, though it seems generally common to refer to such
contraptions (A, B and Y's "Cocoa Programming" contains such usage,
page 81).
I of course mean that the SuperSocket class responds to the -close
method but does not declare it in its interface file.
-close is indeed declared as a method on a SuperSocket category
defined within SuperSocket.m
I was using performSelector: merely to keep the compiler content.
Declaring a further accessible category on SuperSocket to announce the
existence of -close accomplished the same thing.
At least my initial lassitude in declaring that category ultimately
decreased the sum total of my ignorance.
No more super self confusion for me!
On 5 Aug 2008, at 21:39, I. Savant wrote:
On Tue, Aug 5, 2008 at 4:31 PM, James Bucanek
<[EMAIL PROTECTED]> wrote:
The OP did override -close in their subclass and were attempting to
call
[super close] from the subclass' -close method. The OP stated that
they
couldn't simply use [super close] because -close was "private,"
which didn't
make any sense to me.
Yes, I was ignoring that part because I assumed it was just poorly
phrased (and later corrected). Perhaps, Jonathan, you could elaborate
on what leads you to believe the -close method is private?
--
I.S.
_______________________________________________
Cocoa-dev mailing list ([email protected])
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 [EMAIL PROTECTED]
