On Tue, 15 Nov 2005, Sisyphus wrote:
The following code works fine on my Windows2000 box:
use warnings;
print Win32::IsWinNT();
How come it is unnecessary to explicitly load the Win32 module ?
Is it possible to write and install a non-core module in such a way that it
doesn't need to
On Tue, 15 Nov 2005, Sisyphus wrote:
* On Windows ActivePerl will automatically use MinGW to compile modules
if Microsoft VC++ is not installed, but MinGW and dmake are.
Excellent move !!
Presumably a fresh Config.pm, containing values appropriate for MinGW/dmake,
gets written first
- Original Message -
From: Jan Dubois
.
.
We link directly against perl58.dll. We have tested our current setup
with a large list of CPAN modules, and haven't found any that would
build with VC++ but not with MinGW.
Ok ... sounds good. My only doubt was that it seemed to me that
- Original Message -
From: Jan Dubois
.
.
I don't understand why this would be important.
It's only important from a personal point of view - in that it's important
for me to resolve issues that confuse me.
If I had read the appropriate perldoc (ie 'perldoc Win32') properly to begin
On Wed, 16 Nov 2005, Sisyphus wrote:
We link directly against perl58.dll. We have tested our current setup
with a large list of CPAN modules, and haven't found any that would
build with VC++ but not with MinGW.
Ok ... sounds good. My only doubt was that it seemed to me that both EU::MM
Has anyone else ever experienced inconsistencies in digest creation
using the same plaintext? I am encrypting passwords with Digest::SHA1's
sha1_hex function and storing them in a db. When someone logs in, I take
the password, encrypt it the same way and then compare it with the
stored digest.
- Original Message -
From: Wiswell, Virginia
After a few days, Digest::SHA1 starts creating a
different digest for the identical password.
Very unlikely. More likely that the identical password is no longer
identical - and you should be concentrating on finding out how that happens.
I've not had much problems with the digest, even on mp2. This is a wild
shot, but have you tried the OO version of the digest:
$sha1 = Digest::SHA1-new;
$sha1-add($data);
$digest = $sha1-hexdigest;
Wiswell, Virginia wrote:
Has anyone else ever experienced inconsistencies in digest creation
