Identifying ActiveState perl from within a script

[Bill Cernansky]

Does anyone know:

Is there a special variable or available value that can be examined
inside of a perl script that will tell me if the interpreter is
ActiveState?

I know how to get the version. I need the flavor.

I searched quite a bit for this info before coming here. Perhaps it's
just not common knowledge, or I just am not as good at searching as I
think.

 

[Bob Walton]

Bill Cernansky wrote:

....

Is there a special variable or available value that can be examined
inside of a perl script that will tell me if the interpreter is
ActiveState?

I know how to get the version. I need the flavor.

....

One way:

D:\junk>perl -e "print 'AS' if `perl -v`=~/ActiveState/"
AS
D:\junk>

 

[John Bokma]

Does anyone know:

Is there a special variable or available value that can be examined
inside of a perl script that will tell me if the interpreter is
ActiveState?

I know how to get the version. I need the flavor.

I searched quite a bit for this info before coming here. Perhaps it's
just not common knowledge, or I just am not as good at searching as I
think.

using Config?

ccflags='-nologo -Gf -W3 -MD -Zi -DNDEBUG -O1 -DWIN32 -D_CONSOLE -
DNO_STRICT -DHAVE_DES_FCRYPT -DBUILT_BY_ACTIVESTATE -DNO_HASH_SEED -
DUSE_SITECUSTOMIZE -DPERL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS -DUSE_PERLIO
-DPERL_MSVCRT_READFIX'

:
:

cf_email='support#ActiveState.com'

I just wonder why...

 

[Randy Kobes]

Does anyone know:

Is there a special variable or available value that can be examined
inside of a perl script that will tell me if the interpreter is
ActiveState?

For ActiveState Perl, Win32::BuildNumber() will return
the ActivePerl build number.

 

[Bill Cernansky]

First, thanks for the responses, everyone.

I just wonder why...

Mixed development environment caused by merging of two large companies.

We're in the process of dumping a legacy perl (MKS) out of the
environment, but for the time being, we need certain scripts to run
regardless of environment.

MKS perl screws around with backslashes in paths that get sent to
system() or backticked commands. It's crazy that a toolset that is
supposed to provide unix-like functionality actually breaks perl
compatibility.