in reply to Compatability parser?
It's pretty comprehensive (maybe even paranoid, which is not a bad thing in this context). Apart from that, you would at least need to actually put your scripts onto a Windows box that has the suitable version of Perl installed, fire up a command-line prompt window, have a windows port of bash on hand, just to make it easier, and do:perldoc perlport
Get windows ports of other useful things, like grep and sort (or roll your own perl equivalents, since this is typically not much harder than locating the ported code on the web and installing it), in order to go over the *.chk files for common issues.for i in *.pl; do perl -cw $i > $i.chk 2>&1 done
update: Of course, if you use CPAN modules that aren't part of the core perl distribution, that can put a slight damper on portability. In this case, part of your question could be "is there an easy way to distribute portable code so that when recipients install it, it automatically checks for modules it needs and downloads them from CPAN when necessary?" That's a damn good question, and I'm sure someone can suggest a good answer... (I'll check back to look for that.)
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: Compatability parser?
by Anonymous Monk on Nov 19, 2002 at 07:15 UTC | |
by SpaceAce (Beadle) on Nov 19, 2002 at 07:18 UTC |