When you create an executable using perl2exe or PerlApp, the code isn't
actually "compiled" in the sense that you might be thinking. The
interpreter, your code, and all modules are embedded into the exe in such a
way that they can be extracted, linked, and run when you execute the exe.
You may not see perl.exe in there, but the interpreter is still there.
-----Original Message-----
From: Mayank Ahuja
To: Timothy Johnson
Cc: 'Mayank Ahuja '; 'Perl '
Sent: 5/13/02 12:09 AM
Subject: Re: Generalized uname
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???
Thanks Timothy.
Timothy Johnson wrote:
>
> Are you SURE you can't use $^O?
>
> -----Original Message-----
> From: Mayank Ahuja
> To: Perl
> Sent: 5/12/02 11:09 PM
> Subject: Generalized uname
>
> Hi Group!
>
> Is there a module, using which i can determine the Operating System on
> which my perl script is running?
> I cannot use $^O as the my script will be an executable (using
perl2exe)
> and therfore the interpreter won't be available during runtime
>
> I came across a module Sys::Hostname which gives the hostname of the
> machine on all platforms
> Is there an equivalent module for determining the operating system
> (somthing which uses uname on Unix and something else for Windows)
>
> Thanks in advance....
>
> --
> Regards
> Mayank
>
> "The difference between ordinary and extraordinary is that little
extra"
>
-Anon
>
> --
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
Regards
Mayank
"The difference between ordinary and extraordinary is that little extra"
-Anon
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
