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

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


  • Subject: Re: Sending messages without knowing number of args and types at compile time
  • From: Dave DeLong <email@hidden>
  • Date: Tue, 02 Feb 2010 09:17:49 -0700

http://luaforge.net/projects/luaobjc

On Feb 2, 2010, at 9:15 AM, Jens Alfke wrote:

> FYI, there was already a Lua/Obj-C bridge library circa 2006, although I don't remember the name or have a URL handy. (Sorry.)

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________

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: 
 >Sending messages without knowing number of args and types at compile time (From: Per Bull Holmen <email@hidden>)
 >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: Per Bull Holmen <email@hidden>)
 >Re: Sending messages without knowing number of args and types at compile time (From: Jens Alfke <email@hidden>)

  • Prev by Date: Re: Sending messages without knowing number of args and types at compile time
  • Next by Date: Re: NSProgressIndicator Stuck after unhiding + other triggers. Demo App.
  • Previous by thread: Re: Sending messages without knowing number of args and types at compile time
  • Next by thread: Re: bind:toObject:withKeyPath:options: Unidirectional or Bidirectional?
  • Index(es):
    • Date
    • Thread