Re: Understanding the inner workings: getting to know how functions are called
Re: Understanding the inner workings: getting to know how functions are called
- Subject: Re: Understanding the inner workings: getting to know how functions are called
- From: Alastair Houghton <email@hidden>
- Date: Tue, 22 Jan 2008 17:22:54 +0000
On 22 Jan 2008, at 17:17, Jeff Johnson wrote:
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!
:-) Yeah, it's fair to say that the so-called "idiot" approach has a
long and distinguished history. I think we've all done it (or
something similar) at some time or other.
Kind regards,
Alastair.
--
http://alastairs-place.net
_______________________________________________
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