he 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
Ac
On Monday, May 13, 2002, at 12:09 , Mayank Ahuja wrote:
[..]
> $^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'}.
[..]
so why
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 (i
> 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{'os
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 thou
on Mon, 13 May 2002 06:24:46 GMT, [EMAIL PROTECTED] (Timothy
Johnson) wrote:
> Are you SURE you can't use $^O?
ActiveState's PerlApp, which is part of it's Perl Dev Kit, has no
problems whatsoever with $^O.
--
felix
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-m
> I've never used perl2exe, I don't know much about it, but are
> you 100% sure the interpreter isn't available? That'd make
> every eval{} invalid... and certainly a lot of code uses it.
>
> Try compiling code with:
>
> eval { print $^O }
>
> and see what happens.
Opps, change {} to "", ev
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
> 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've never used perl2exe, I don't know much abou
