> ooopss!! i was wrong ... $^O worked....
>
> According to "perldoc perlvar" :
>
> $^O The name of the operating system under which this
> copy of Perl was built, as determined during the
> configuration process. The value is identical to
> $Config{'osname'}.
>
> I thought perl2exe won't be able to use $^O because the
> copy of the Perl won't be available during run time
>
> But it worked... I don't know how....
> Any ideas???
It is obvious:
The only program that parses Perl is perl, and to really be
Perl you also have to be perl. The easiest way to turn
Perl code into an executable is to embed the perl interpreter!
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).
Jonathan Paton
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
