Re: Silly question on extending NSObject.

> On Feb 20, 2019, at 5:11 PM, Alex Zavatone wrote: > > 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. The warning/error is just

Re: Silly question on extending NSObject.

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

Re: Silly question on extending NSObject.

> On Feb 19, 2019, at 7:23 PM, Alex Zavatone wrote: > > >> On Feb 19, 2019, at 4:15 PM, Jens Alfke wrote: >> >> >> >>> On Feb 19, 2019, at 1:23 PM, Alex Zavatone >> > wrote: >>> >>> In most Objective-C projects I add an autodescribe category on NSObject and >>> put

Re: Silly question on extending NSObject.

> On Feb 19, 2019, at 4:15 PM, Jens Alfke 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

Re: Silly question on extending NSObject.

> On Feb 19, 2019, at 4:15 PM, Jens Alfke wrote: > > > >> On Feb 19, 2019, at 1:23 PM, Alex Zavatone > > wrote: >> >> In most Objective-C projects I add an autodescribe category on NSObject and >> put the import for the category header into a .pch for the project so

Re: Silly question on extending NSObject.

> On Feb 19, 2019, at 3:37 PM, Rob Petrovec wrote: > > Why not use/override -description or -debugDescription instead of > re-inventing the wheel? > > —Rob I prefer having something that I know is for a specific purpose. ___ Cocoa-dev mailing

Re: Silly question on extending NSObject.

On 19. feb. 2019, at 1:23 e.h., Alex Zavatone wrote: > In most Objective-C projects I add an autodescribe category on NSObject and > put the import for the category header into a .pch for the project so that it > will be available for every class in the project. > > This lets me dump an

Re: Silly question on extending NSObject.

> On Feb 19, 2019, at 1:23 PM, Alex Zavatone wrote: > > In most Objective-C projects I add an autodescribe category on NSObject and > put the import for the category header into a .pch for the project so that it > will be available for every class in the project. > This lets me dump an

Re: Silly question on extending NSObject.

Rob, how, exactly, would Alex do that such that all objects inheriting from NSObject will automatically have the implementation, which seems to be the goal? The issue with .pch, as I understand it, is that Xcode wants to get away from using precompiled headers, and there are various

Re: Silly question on extending NSObject.

Why not use/override -description or -debugDescription instead of re-inventing the wheel? —Rob > On Feb 19, 2019, at 2:23 PM, Alex Zavatone wrote: > > Sorry. Second try. > > In most Objective-C projects I add an autodescribe category on NSObject and > put the import for the category header

Re: Silly question on extending NSObject.

Sorry. Second try. In most Objective-C projects I add an autodescribe category on NSObject and put the import for the category header into a .pch for the project so that it will be available for every class in the project. This lets me dump an object’s properties and values at Will in the