Lately I've been *using* Inline instead of working on it. And I've
noticed something. Inline works well in the following situations:
- Writing new C code in Perl.
- Binding Perl to old (stable) external C libraries.
Where it doesn't do as good is when you are developing an external
library *and* developing Inline C/Perl at the same time. The problem is
that when you recompile the external stuff, the Inline stuff doesn't
automatically recompile. You need to remember to use the 'FORCE'
option/shortcut to rebuild it.
One way to solve this is with a 'DEPS' option where you say something
like:
use Inline C => DATA =>
DEPS => ['./lib/foo.so', './lib/bar.so'];
Inline could check to make sure that its own shared object is more
current than the dependencies, or force a rebuild. Of course, what you
probably relly mean is:
use Inline C => DATA =>
MYEXTLIB => ['./lib/foo.so', './lib/bar.so'],
DEPS => ['./lib/foo.so', './lib/bar.so'];
so maybe MYEXTLIB could automatically add to the DEPS. DEPS would just
be used for other things like header dependencies.
Any thoughts?
Brian
--
perl -le 'use Inline C=>q{SV*JAxH(char*x){return newSVpvf
("Just Another %s Hacker",x);}};print JAxH+Perl'
