Re: Creating a subclass of an *unknown* object
Re: Creating a subclass of an *unknown* object
- Subject: Re: Creating a subclass of an *unknown* object
- From: Ofri Wolfus <email@hidden>
- Date: Wed, 15 Jun 2005 11:52:25 +0300
Category has the same problem plus another one - there is no easy way
to call [super doOriginalMethod].
The only solution i can think of is to do "method swizzling" and
replace specific methods of the original object while keeping a
reference to the original one and call it when needed. This seems a
bit too complicated though...
- Ofri
On 15/06/2005, at 11:40, Stefan Schüßler wrote:
Maybe you can use a category instead of posing.
Stefan
Am 14.06.2005 um 22:51 schrieb Ofri Wolfus:
Hi all,
I'm creating a plugin for an application in which is not mine but
is open source so i have the code for it.
What i'm trying to do is to subclass an object that's within the
app and when my plugin is loaded, to pose it as the original
object. The problem is that i'm getting an undefined symbol error
when when compiling my plugin.
I *could* include the header and implementation files of the
original object within my plugin, but this means that if in a
future version this object will change and my plugin will be
loaded, both versions of the object will be loaded and this is not
a good thing.
What should I do?
- Ofri
_______________________________________________
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