"Kort, Eric" wrote:
> 
> > Thanks for your input.
> > However, I can't do that for 2 reasons :
> > - 1st (bad) reason : my modules are already written -- I would have to
> > re-write them ;
> > - 2nd (good) reason : Inline is not ported to MacOS : I would have to
> > maintain 2 different versions of my source code...
> >
> > Hence, I *have* to compile my modules myself...
> 
> a. Why can't you just cut and paste your existing source code into the perl
> scripts as inline'd C?  You would still have two "versions" (one inline'd
> for Win32, one not for Mac) but the C source in the two versions would be
> identical.  Or are you using Mac-specific code elements?  In that case, you
> would have to recode anyway for the Windows API.

Some points:
1) Inline just writes XS for you and then throws it away after
compilation. If you want to use XS, you may as well let Inline give you
a helping hand. Use the INFO and NOCLEAN options, and look into the
build area.
2) Inline is a couple of months away from having rock-solid module
authoring support. Even I would suggest waiting for release v0.40,
before submitting Inline-based modules to CPAN.
3) Does anyone know the issues of why Inline doesn't work with MacOS?
The only thing I can think of is that the latest version of Perl is
5.004 on Mac (AFAIK). Inline requires 5.005, but only because
Parse::RecDescent requires it. If you could find out what the last
version of Parse::RecDescent that supported 5.004 was (Damian?), it
might be a simple matter to port Inline to the Mac. Porting Inline to
Win32 only required a dozen lines of code to change. Mostly to deal with
'C:' at the start of path names.
4) In the future you'll *really* want to use Inline over XS/SWIG for
writing modules on platforms like Mac or Win32, which don't have
compilers installed on the average installation. That's because there
will be dead-simple support for creating binary module distributions.

Cheers, Brian

-- 
perl -le 'use Inline C=>q{SV*JAxH(char*x){return newSVpvf
("Just Another %s Hacker",x);}};print JAxH+Perl'

Reply via email to