Re: Multiple Inheritence (Was: Is _objc_flush_caches_(Class) necessary to swizzle methods?)
Re: Multiple Inheritence (Was: Is _objc_flush_caches_(Class) necessary to swizzle methods?)
- Subject: Re: Multiple Inheritence (Was: Is _objc_flush_caches_(Class) necessary to swizzle methods?)
- From: Ondra Cada <email@hidden>
- Date: Sat, 25 Sep 2004 05:07:09 +0200
On 25.9.2004, at 4:52, DumberThanDanQuayle wrote:
Great, this now explains the ivar related problem I noticed and
basically _rules out_ method swizzling for what I am trying to
accomplish here, which is merely writing a method or protocol
implementations only once, instead of multiple times (once for each
class with a different super-class). Given that these classes needing
a common method implementation have different super-class, they often
have different ivar structures as well.
I do not care about classes "looking" like other classes here, that is
easily accomplished with protocols (or other techniques like
"+poseAsClass" or message forwarding as you mentioned). I am merely
looking for a way to write implementations once and then use them in
ostensibly unrelated classes. This is barely multiple inheritance.
At the first look, kinda sounds like a plain common-ancestor (like
NSObject, if nothing other) category might help here?
Or some refactoring perhaps :)))
---
Ondra Čada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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