On Sun, Mar 9, 2008 at 7:34 AM, Terje Bless <link@pobox.com> wrote:

Hmm. Do you actually need to run the /usr/bin/perl built for the
iPhone, or do you need to link them against the libperl that's
built for the iPhone?

The latter will suffice, if we can live without "make test". We could conceivably create new targets in Xcode to build the module, instead of using ExtUtils::MakeMaker as it's done now. It shouldn't be hard, with EU::MM already showing us exactly what compiler flags we need to use. We could use Xcode's built-in unit testing too, instead of calling "make test", should that prove necessary and possible.

BTW, Sherm, you didn't consider writing up a CamelBones related
proposal for Kleiner Perkins did you? :-)

Are you kidding me? I've been racking my brain for ideas. :-)

I have a few ideas, actually. For instance, an app that used DBD::Proxy (pure perl, so no compilation worries) could allow for wireless access to an Oracle, DB2, or any other database. That would certainly help make the iPhone into a useful tool for businesses.

  <http://www.kpcb.com/initiatives/ifund/>

With a cool $100M in venture capital to spread around, it should
be within their risk-taking levels to start a small Perl on
iPhone company.

I'm not CEO material, myself, and I know jack about marketing a product. I can estimate how much it may cost to build an app, in terms of programmer salary, but I don't have a clue what a reasonable marketing budget might be for it. But if someone who *is* blessed with those skills needs a developer for such a venture wants to talk partnership, I'm all ears. :-)

sherm--