Hi. U can't do that because Perl must autovivify $Config{bar} in order to
have a value to put into $_. HTH.
At 08:54 PM 2/21/2011 +0100, Christian Walde wrote:
use Config;
# print 1 if $Config{foo}; # enabling this removes the crash
grep { $_ } $Config{bar}; # this crashes
On Tue, 22 Feb 2011 13:46:55 +0100, Chris Wagner wagn...@plebeian.com wrote:
At 08:54 PM 2/21/2011 +0100, Christian Walde wrote:
use Config;
# print 1 if $Config{foo}; # enabling this removes the crash
grep { $_ } $Config{bar}; # this crashes
These two lines on their own will
Jan,
Your builtin link() is a godsend! If only I'd known years ago I
could have saved a lot of heartache trying to kludge
Win32::API::Prototype into working in my programs.
I did a lot of testing of link() over this last weekend, and got mixed
results. Here's my test environment:
Is there a simple way to determine what flavor of PERL is running from
within a program, specifically one that is wrapped within PERLAPP? In
other words, I need to determine if the PERL is 32-bit or 64-bit, to
determine if it is running in WoW64 or not. I realize it is easy to
determine the
Load Config.pm and look at $Config{ptrsize}. It is either 4 or 8, telling you
that you are running 32-bit or 64-bit Perl.
Cheers,
-Jan
From: perl-win32-users-boun...@listserv.activestate.com
[mailto:perl-win32-users-boun...@listserv.activestate.com] On Behalf Of
Michael Cohen
Sent:
Jan,
Thanks a lot!! That did the trick.
Regards,
Michael Cohen
From: Jan Dubois j...@activestate.com
To: Michael Cohen/Raleigh/IBM@IBMUS,
perl-win32-users@listserv.ActiveState.com
Date: 02/22/2011 04:18 PM
Subject:RE: Pulling PERL Exectuable x86 vs x64
Load Config.pm
On Tue, 22 Feb 2011, Brian H. Oak wrote:
Your builtin link() is a godsend! If only I'd known years ago I
could have saved a lot of heartache trying to kludge
Win32::API::Prototype into working in my programs.
Looks like I added support for it in 1999:
Quoting Jan Dubois j...@activestate.com:
I suspect that you are doing some operation that is not updating a file,
but deleting and re-creating it. This will always break hard links.
I went over my test methodology with a fine-tooth comb, and discovered
that I had indeed messed up the order
