Oh, I'm sure it does. I haven't used it in awhile (my current company is a Linux shop, so I'm blissfully removed from Windows now), but my experiences with Active State all indicate that they are above doing that sort of thing.For example, when I got the license for the developer's kit, I was happy to see that it permits the user to run it on multiple computers, as long as it's just one at a time. This, in contrast with the software licenses of many other places, which forbid installing on other than a single computer.
@ARGV=split//,"/:L";
map{print substr crypt($_,ord pop),2,3}qw"PerlyouC READPIPE provides"
| [reply] |
If I remember rightly, the AS perlapp creates a fully functional .exe, but it has like a 5-second pause and shows a "You're using a trial version" banner before it exectutes. You can send it to your client and if it works, buy the full Dev Kit and get him the non-pause program.
Something I thought of: To test for dependencies, go find perl58.dll in your Windows directory and rename it. Then rename c:\perl to c:\Notperl or something. If you can't run your packaged script with all dependent paths cut off, then the problem is likely in what you're packaging. See above messages for where to look.
--marmot | [reply] |
Two very useful suggestions, thank you.
($_='kkvvttuu bbooppuuiiffss qqffssmm iibbddllffss')
=~y~b-v~a-z~s; print
| [reply] |