Re: run-time list of selectors in protocol?
Re: run-time list of selectors in protocol?
- Subject: Re: run-time list of selectors in protocol?
- From: Jeff LaMarche <email@hidden>
- Date: Fri, 9 Dec 2005 13:31:29 -0500
On Dec 9, 2005, at 1:26 PM, Damien Bobillot wrote:
We are developing an application with a number of plugin
interfaces. The customer is government, so I can't go into much
detail about what the app does, but one requirement is that it be
as easy as possible for third parties to develop the plugins.
Currently there are 2 plugin types, with an expectation that we
will add 1-2 more. Each plugin has its own protocol.
If a method is optional for the plugin, or a plug-in could
conceivably work, you could also consider making the method part of
an informal protocol, and only put those that are truly required as
part of the formal protocol. I understand your concern, especially
working on a government contract, but it seems like you have so much
responsibility to make sure someone else's code works. =-) If the
truly required methods were in a formal protocol, then you could use
conformsToProtocol: and if it doesn't, you could issue a warning
saying something like "Plugin 'X' may be outdated or missing
functionality".
Just my 2ยข without knowing enough about your project to have an
informed opinion. :-) _______________________________________________
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