Besides, while running it does not extract anything anywhere.
in reply to Re: Re: The Perl Compiler (turning perl scripts into binary executables)
in thread The Perl Compiler (turning perl scripts into binary executables)
I respectfully disagree. The free-standing executable's @inc paths are . and %temp%\scriptname\uniqueid.
The subdirectory contains perl56.dll and perlapp.dll which looks like the interpreter (based on file size) + some other goodies.
Update: I didn't mean to imply that all of the script-dependent modules are in the subdirectory. They aren't. Now I wonder what's going on in Linux and Solaris.
I've seen WinNT errors thrown when a stand-alone script is run without proper permissions(actually, wrong user). The error stated that Perl.exe was causing it. I hope I saved a screen shot of it somewhere...
You're right Jouke, I don't know exactly how it works. I'm just gues^H^H^H^H reasoning it out. The Win32API that needs NT to build, but not to run has me stumped. Hopefully Win9x/ME will be dead before anyone would want to use the perl monk compiler on it.