What's with these redundant methods ?
What's with these redundant methods ?
- Subject: What's with these redundant methods ?
- From: MarketLogix Developer <email@hidden>
- Date: Tue, 22 Apr 2003 09:02:54 -0700
Hi.
In continuing with my ports to OS X I have come across an 'interesting'
situation with gdb.
When trying to gdb-execute a method like [myCollection count] to
inspect the retval, I got
a MyCollection class does not recognize -> respondsToSelector: and
methodForSelector: .
Well, true I do not implement those but Object from the ObjC runtime
does implement
respondsTo: and methodFor: and any class that I implement will inherit
from Object and
so inherit these. I worked around this gdb stopper by implementing
respondsToSelector:
and methodForSelector: in a category where they simply call respondsTo:
and methodFor: .
Why do we now have 2 different implementations of the EXACT same darn
method ?
What other silly gdb only (re)implementaions can I expect ?
-----------------------------------------------
bisk ~ OSX.2.4
G4 PowerMac Gigabit, Dual 500
Sony SDM-M81 18.1" LCD display
1GB, 40GB, SuperDrive(DVR 105)
HP "All-in-One" d135 BubbleJet
-----------------------------------------------
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.