Re^4: I need to know if 32-bit or 64-bit perl is running my script.

[Tux]

The first two are CORE capabilities since perl5.003_07. Sorry to sound harsh, but whining that you cannot install from CPAN is bullshit, that is repeated over and over and over again with all possible workarounds here on PM.

Nagging about startup time might be true for Config::Perl::V, which does quite a bit more than we'd love to just to be able to get the info (not true anymore on perl-5.18, where that info is available directly from CORE, as is Config::Perl::V). The extra time you see is the dumper time, which was just used to show you the content. Try again with just accessing the data required and you will see a considerable speedup. IMHO all those speeds are just noise in the complete picture, but I do not want to compare apples and pears.

Nagging about Config is just trying to find sand to throw into the engine. You have no idea how many modules use Config, so it will be loaded anyway sooner or later.

$ find 5.18.0 -name \*.pm | xargs grep -wl 'use Config' | wc -l
57
$ find site_perl/5.18.0 -name \*.pm | xargs grep -wl 'use Config' | wc
+ -l
107
$ corelist Config Config::Perl::V

Data for 2013-08-20
Config was first released with perl 5.00307

Data for 2013-08-20
Config::Perl::V was first released with perl v5.17.9
$ time perl -V:ptrsize
ptrsize='4';
0.005u 0.003s 0:00.00 0.0%      0+0k 0+0io 0pf+0w
$ time perl -MConfig -wE'say $Config{ptrsize}'
4
0.001u 0.005s 0:00.00 0.0%      0+0k 0+0io 0pf+0w
$ time perl -MConfig::Perl::V -wE'say Config::Perl::V::myconfig ()->{c
+onfig}{ptrsize}'
4
0.007u 0.002s 0:00.00 0.0%      0+0k 0+0io 0pf+0w

[flexvault]

Tux,

The first two are CORE capabilities since perl5.003_07. Sorry to sound harsh, but whining that you cannot install from CPAN is bullshit, that is repeated over and over and over again with all possible workarounds here on PM.

What an arrogant response!

I guess you've been passed over for management a few times and it shows. So let us take you're two statements, both false. First, those non-core capabilities had to be downloaded from CPAN. I used a Perl 5.14.2 on a test server, so I went to a production machine and:

> /usr/opt/perl5.12.2/bin/perl -v

This is perl 5, version 12, subversion 2 (v5.12.2) built for aix

Copyright 1987-2010, Larry Wall
 . . .


> /usr/opt/perl5.12.2/bin/perl -MData::Peek -MConfig::Perl::V -we 'DDu
+mper (Config::Perl::V::myconfig()->{config})'
Can't locate Data/Peek.pm in @INC (@INC contains: /usr/opt/perl5.12.2/
+lib/site_perl/5.12.2/aix /usr/opt/perl5.12.2/lib/site_perl/5.12.2 /us
+r/opt/perl5.12.2/lib/5.12.2/aix /usr/opt/perl5.12.2/lib/5.12.2 
.).
BEGIN failed--compilation aborted.
>

And the second part that you obviously didn't understand, is that it's not a technical problem, but a management rule. The easiest way to get fired at my company is to load anything on a production server without going through a code review.

Thank you...Ed

[Anonymous Monk]

So let us take you're two statements, both false. First, those non-core capabilities had to be downloaded from CPAN.

The first two things listed are

$ perl -V:ptrsize
ptrsize='8';
$ perl -MConfig -wE'say $Config{ptrsize}'
8

which is available since 5.00307 since 5.003_07 1996-Oct-10

What an arrogant response!

Dudue :) after you hear it 20k times ... even if its a job requirement ... its like a taboo

[Jenda]

Fine. Code review the module! If it's not part of the Perl installation, make it part of the project.