• 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: Harnessing Perl Scripts within a Project
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Harnessing Perl Scripts within a Project


  • Subject: Re: Harnessing Perl Scripts within a Project
  • From: Mark Aufflick <email@hidden>
  • Date: Wed, 07 Nov 2012 14:12:30 +1100

In fact it is very possible to effectively bridge Perl and Cocoa objects
since Perl embeds very nicely in multi-threaded C based parents. Apple
provides (provided?) a fairly good bridge but it has some leaks & isn't
well maintained. There is also CamelBones as mentioned. I wrote my own that
has full KVO and bindings support and while it may be open sourced one day
it's not too hard to achieve the basics like calling functions and methods.
(Having said that, while there's nothing too complex about it, without a
thorough understanding of C you will struggle, but then you're going to
want that to become a productive Cocoa developer anyway).

Take a look at perlcall and perlembed http://perldoc.perl.org/perlcall.html
http://perldoc.perl.org/perlembed.html and feel free to ping me with any
questions.

--
Mark Aufflick
 http://mark.aufflick.com/about/contact
 http://pumptheory.com/about



On Wed, Nov 7, 2012 at 1:19 PM, Jens Alfke <email@hidden> wrote:

>
> On Nov 6, 2012, at 4:03 PM, Andres Kievsky <email@hidden> wrote:
>
> > I'm curious - isn't the fact that none of those languages support true
> multithreading a rather big hindrance when programming a Cocoa Application?
> How would you put together a responsive application without it?
>
> Threading isn’t mandatory. Most of the slow stuff like network I/O can be
> done with asynchronous APIs. (On the other hand, my app development has
> been done on Mac OS, not iOS, and I know iOS devices have a lot fewer CPU
> cycles to throw around…)
>
> Anyway, if responsiveness is a concern, you probably don’t want to be
> coding in any interpreted language! Back in the day (1998-2000) my team and
> I were struggling to get Java to perform well compared to native apps, and
> even back then Java had considerably better performance than purely
> interpreted ‘scripting’ languages.
>
> —Jens
> _______________________________________________
>
> 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
>
_______________________________________________

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: 
 >Harnessing Perl Scripts within a Project (From: John Delacour <email@hidden>)
 >Re: Harnessing Perl Scripts within a Project (From: Fritz Anderson <email@hidden>)
 >Re: Harnessing Perl Scripts within a Project (From: John Delacour <email@hidden>)
 >Re: Harnessing Perl Scripts within a Project (From: Jens Alfke <email@hidden>)
 >Re: Harnessing Perl Scripts within a Project (From: John Delacour <email@hidden>)
 >Re: Harnessing Perl Scripts within a Project (From: Andres Kievsky <email@hidden>)
 >Re: Harnessing Perl Scripts within a Project (From: Jens Alfke <email@hidden>)

  • Prev by Date: Re: Harnessing Perl Scripts within a Project
  • Next by Date: Re: CALayer still has no constraints on iOS
  • Previous by thread: Re: Harnessing Perl Scripts within a Project
  • Next by thread: Re: Harnessing Perl Scripts within a Project
  • Index(es):
    • Date
    • Thread