Re: The SampleCMPlugin example
Re: The SampleCMPlugin example
- Subject: Re: The SampleCMPlugin example
- From: Rosyna <email@hidden>
- Date: Sun, 3 Mar 2002 16:15:48 -0700
This is an extremely annoying "feature" of Obj-c. Means that no
application can do runtime updating of plugins without keeping the
old plugins resident in memory. (and probably on disk)
Ack, at 3/4/02, Dietmar Planitzer said:
I think this 'of course' should actually be a 'it depends'.
Namely, it depends on whether the (Carbon) host application is ever going to
unload your ObjC based plug-in. If it does so, then your plug-in will blow
up the app because the ObjC runtime system doesn't support the unloading of
code and worse it actively installs a dyld callback which gets called as
soon as someone tries to unload one of your ObjC code segments. This
callback will then happily kill the host application. Note that it doesn't
matter whether you use the AppKit or Foundation kit, just a small class
derived from good old Object will suffice to get users very angry :)
This isn't an issue for Cocoa host applications because NSBundle doesn't
even offer API for unloading.
--
Sincerely,
Rosyna Keller
Technical Support/Holy Knight/Always needs a hug
Unsanity: Unsane Tools for Insane People
---
Please include any previous correspondence in replies, it helps me
remember what you're talking about. Thanks.
_______________________________________________
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.