• 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: ObjC in time-critical parts of the code
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ObjC in time-critical parts of the code


  • Subject: Re: ObjC in time-critical parts of the code
  • From: Michael Ash <email@hidden>
  • Date: Sun, 18 Jan 2009 23:56:30 -0500

On Sun, Jan 18, 2009 at 9:23 PM, Ben Trumbull <email@hidden> wrote:
> Several work arounds exist.  The easiest is to create a static C member
> function (yes, ObjC has member *functions* which most people overlook).

Well no, it doesn't. ObjC has functions, by virtue of being a superset
of C, but it does not have "member functions". You can write functions
that are logically associated with a class, but this is a human
construct, not one that the compiler knows about. It's a useful
technique to be sure, but it's important to realize that from the
language point of view these are just standard C functions, nothing
more.

Mike
_______________________________________________

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: 
 >Re: ObjC in time-critical parts of the code (From: Ben Trumbull <email@hidden>)

  • Prev by Date: Re: bindings and sub array modification notification.
  • Next by Date: Re: Memory allocation issues with NSObject and NSString
  • Previous by thread: Re: ObjC in time-critical parts of the code
  • Next by thread: Re: ObjC in time-critical parts of the code
  • Index(es):
    • Date
    • Thread