• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Is this the correct way to cache an IMP?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Is this the correct way to cache an IMP?

  • Subject: Re: Is this the correct way to cache an IMP?
  • From: Ken Thomases <email@hidden>
  • Date: Thu, 5 Aug 2010 10:55:40 -0500
> On 05/08/2010, at 11:12 PM, Jean-Daniel Dupas wrote:
>
>> Probably not faster, but cleaner IHMO:

Actually, I suspect it is faster.  All function invocations are direct rather than indirected through a pointer.  This is faster in and of itself and also allows the compiler to recognize the recursion and optimize it.  Of course, measuring of the performance or inspection of the generated assembler is the only way to be sure.

Regards,
Ken

_______________________________________________

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
References: 
 >Is this the correct way to cache an IMP? (From: Graham Cox <email@hidden>)
 >Re: Is this the correct way to cache an IMP? (From: Jean-Daniel Dupas <email@hidden>)
 >Re: Is this the correct way to cache an IMP? (From: Graham Cox <email@hidden>)

  • Prev by Date: Re: Resolution of an NSImage(Rep)?
  • Next by Date: Re: AttributedString from NSData on iPhone.
  • Previous by thread: Re: Is this the correct way to cache an IMP?
  • Next by thread: Re: Is this the correct way to cache an IMP?
  • Index(es):
    • Date
    • Thread