Skip navigation.
 
mlRe: Understanding the inner workings: getting to know how functions are called
FROM : Jeff Johnson
DATE : Tue Jan 22 18:17:12 2008

On Jan 22, 2008, at 10:05 AM, Mattias Arrelid wrote:

> The "idiot" way of implementing this could of course be to add 
> _all_ method names of the class in question and then just call 
> [super methodName] in each method, and then use some debug macro 
> before and after that call that prints the name of the method in 
> question. That really isn't that productive and seems like a waste 
> of time.
>


Hey, I resent that characterization!

http://lapcatsoftware.com/blog/2007/03/10/everything-you-always-
wanted-to-know-about-nsapplication/

Related mailsAuthorDate
mlUnderstanding the inner workings: getting to know how functions are called Mattias Arrelid Jan 22, 17:05
mlRe: Understanding the inner workings: getting to know how functions are called Kyle Sluder Jan 22, 17:26
mlRe: Understanding the inner workings: getting to know how functions are called Bill Bumgarner Jan 22, 17:33
mlRe: Understanding the inner workings: getting to know how functions are called Alastair Houghton Jan 22, 17:56
mlRe: Understanding the inner workings: getting to know how functions are called Jeff Johnson Jan 22, 18:17
mlRe: Understanding the inner workings: getting to know how functions are called Alastair Houghton Jan 22, 18:22
mlRe: Understanding the inner workings: getting to know how functions are called Mattias Arrelid Jan 22, 20:34
mlRe: Understanding the inner workings: getting to know how functions are called Mattias Arrelid Jan 23, 09:38
mlRe: Understanding the inner workings: getting to know how functions are called Mattias Arrelid Jan 23, 10:43
mlRe: Understanding the inner workings: getting to know how functions are called Bill Bumgarner Jan 23, 17:22
mlRe: Understanding the inner workings: getting to know how functions are called Mattias Arrelid Jan 23, 18:25