on Mon, 13 May 2002 07:21:31 GMT, [EMAIL PROTECTED] (Jonathan
e. paton) wrote:
> Thus, your original program is compiled into Perl bytecode,
> and is then run through a full interpreter - you have all the
> power of Perl. However, this means perl2exe is a poor way to
> increase speed (in fact, it's worse than normal - as memory would
> normally be shared between interpreters on Unix, which won't
> happen if you have several scripts in exe form).
Don't know about perl2exe, but the ActiveState's PerlApp user guide
states:
PerlApp is not a compiler. That is, the Perl source code and the
contents of embedded modules must be parsed and compiled on the
fly when the executable is invoked. However, PerlApp makes it
easier to distribute Perl scripts, as Perl (or a specific version
and combination of Perl modules) does not need to be resident on
the target system. PerlApp applications will not run any faster
than the source Perl script.
It is the fact that a client machine doesn't need a full Perl
installation for these programs to work that makes these tools useful
to me. Consider e.g. the deployment of a program to a large number of
(business) users.
--
felix
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
