On 01-Mar-2010, at 7:34 PM, Uli Kusterer wrote: > On 01.03.2010, at 12:05, Roland King wrote: >> Firstly if that's what happened, the program would recurse, the stack would >> be full of textViewDidChangeSelection: calls each calling the next, but that >> is not what happens, the program hangs, the code infinitely loops, but it >> does not recurse, the stack stays about 20 stack frames deep. > > > I haven't read that thread, so you may well be true, but just going by your > description, tail recursion optimizations, as well as IMP cacheing, could > cause the behaviour you're observing. >
That is true, if the method actually existed at all and was called and recursed, those optimizations could look like that, thanks for pointing it out. In this case there's the extra point that the method doesn't actually exist and it's not being called at all (it's just being checked for in respondsToSelector:)_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
