• 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
Sending messages without knowing number of args and types at compile time
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Sending messages without knowing number of args and types at compile time


  • Subject: Sending messages without knowing number of args and types at compile time
  • From: Per Bull Holmen <email@hidden>
  • Date: Mon, 1 Feb 2010 03:30:08 -0800 (PST)

Hi

I've been playing around with the idea of making a simple bridge between Objective-C (running under Cocoa) and a script language. Not for the API, that is, but for user defined classes and methods. For this reason, I'd like to know whether there are any other ways than NSInvocation to send a message without knowing arg types and numbers at compile time. Non-hackish ways, that is. I see that people used objc_msgSendv earlier, but it is no longer available in Objective-C 2.0. Also, using objc_msgSend doesn't seem to be platform independent (PPC/Intel). So, does this mean that NSInvocation is the only civilised way to go? NSInvocation is great, it's just that there's a lot of overhead, so I assume this is because it has functionality I might not need?

Per
_______________________________________________

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

  • Follow-Ups:
    • Re: Sending messages without knowing number of args and types at compile time
      • From: Greg Parker <email@hidden>
    • Re: Sending messages without knowing number of args and types at compile time
      • From: Michael Ash <email@hidden>
    • Re: Sending messages without knowing number of args and types at compile time
      • From: Jens Alfke <email@hidden>
  • Prev by Date: Re: NSDocument override Undo's default handling of changes count
  • Next by Date: Re: bind:toObject:withKeyPath:options: Unidirectional or Bidirectional?
  • Previous by thread: Re: NSDocument override Undo's default handling of changes count
  • Next by thread: Re: Sending messages without knowing number of args and types at compile time
  • Index(es):
    • Date
    • Thread