Re^3: why is there no a PVM for perl? (avoiding native code)

> A multitude depends on an specific underlying function call or program, often only found in the Linux world. The use of a XS interface, often present in the modules without any mention in the documentation, can really break portability.

IMHO you are idealizing JAVA now, because use of native libraries causes the same problems there.

For much the same reasons I try to avoid modules using XS. Just inspect the dependencies in CPAN and parse the code for DynaLoader to do so.

Cheers Rolf

Comment on Re^3: why is there no a PVM for perl? (avoiding native code)

Replies are listed 'Best First'.
Re^4: why is there no a PVM for perl? (avoiding native code) by Anonymous Monk on Jun 03, 2011 at 00:06 UTC
For much the same reasons I try to avoid modules using XS. like I said above, Cwd is standard module shipped with perl, but it can't still be updated with ease. I can't imagine how handle other less-tested modules. Second, the situation which a perl user have to use make to install module is a little ridiculous too. Module::Build has existed almost 10 years, but it seems few guys try it.	[reply]
Re^5: why is there no a PVM for perl? (avoiding native code) by zwon (Abbot) on Jun 03, 2011 at 15:08 UTC
Module::Build has existed almost 10 years, but it seems few guys try it. I personally find typing `./Build` very hard comparing to `make`, they could at least call it `./build`, yet better they could install `build` somewhere in the `$PATH`. Also typing `./Build test` to make test is kinda unnatural ;)	[reply] [d/l] [select]