> 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.
Obviously, it's up to you. But for the moment I persist in my view that
simply cutting and pasting your existing code Inline style will be a lot
less of a headache than using SWIG or h2xs. But if you insist:
b.
perldoc h2xs
perdoc perlapi
perldoc perlxs
perldoc perlxstut
perldoc perlguts
www.swig.org
If neither a nor b are sufficient, please advise.
