Re: Silly question on extending NSObject.
Re: Silly question on extending NSObject.
- Subject: Re: Silly question on extending NSObject.
- From: Alex Zavatone <email@hidden>
- Date: Wed, 20 Feb 2019 19:11:16 -0600
Odd. I just looked at a test app I have for testing the autoDescribe extension
to NSObject in Xcode 10.1 for iOS.
Commenting out #import “NSObject+AutoDescribe.h” in the .pch does cause an
invalid selector build error if autoDescribe is used in any class file, but you
can enter it on an object from the debugger.
po [thisObject autoDescribe]
Sent from my iPhone
> On Feb 19, 2019, at 8:31 PM, Alex Zavatone <email@hidden> wrote:
>
>
>>> On Feb 19, 2019, at 4:15 PM, Jens Alfke <email@hidden> wrote:
>>>
>>> Is there a more modern way to do this than using a .pch?
>>
>> You don’t need a PCH for this. If you declare the category in an @interface
>> or @implementation that gets parsed as part of your target, it’ll exist.
>> Same for the methods in the category. It doesn’t matter whether the
>> interface is parsed in every source file or not.
>>
>> —Jens
>
> Well, I’ll be. It appears you are correct. Now, why was it that a few years
> back, I ended up thinking that I needed to import it to get it to work?
> Hmmmm.
>
>
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> 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:
>
> This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden