The @dynamic keyword tells the compiler not to worry about it (i.e. you are promising it that you are going to handle those selectors).
Thanks, Jon On Feb 25, 2014, at 3:14 PM, jonat...@mugginsoft.com wrote: > > On 25 Feb 2014, at 21:38, Greg Parker <gpar...@apple.com> wrote: > >> On Feb 25, 2014, at 6:42 AM, jonat...@mugginsoft.com wrote: >>> I have an NSString subclass as below. >>> If the subclass doesn’t respond to a given selector I want to forward the >>> selector to another object. >>> >>> What is the best way to declare the interfaces for DBManagedString and >>> DBManagedObject? >>> >>> Should I declare a DBManagedObject protocol in which all the methods are >>> optional? >> >> A protocol works. >> >> Declaring the methods without implementing them also works. > Will the complier not complain about the missing implementations? > > Jonathan > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/cocoa-dev/jhull%40gbis.com > > This email sent to jh...@gbis.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
