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 wrote:
>
>> On Feb 25, 2014, at 6:42 AM,
On 25 Feb 2014, at 21:38, Greg Parker 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
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
> DBManagedObje
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 method
