Re: dynamic loading modules

[fishmonger]

Have you taken a look at using Module::Load::Conditional? http://search.cpan.org/~bingos/Module-Load-Conditional-0.54/lib/Module/Load/Conditional.pm

[sdetweil]

sorry, thats again off the mark..

how do I code the source statement calling the function in the module AFTER I change from hard coded to dynamic loading?

this part seems to be missing in any text I read..

my app today uses

my $os = Win32::GetOSName();

there is NOT a 'use win32' anywhere.. I know, I coded it all. I don't know if there is some OTHER method loading this module.

regardless..

coding explicitly Win32::GetOSName() gets me into trouble, so I ASSUME I have to change the code.. to WHAT?

just my $os=GetOSName() fails. how is the compiler supposed to set this up for dynamic resolution vs static? thats what I'm asking for.

[fishmonger]

Unless I'm misunderstanding your goal, I don't see any reason why you can't use Module::Load or Module::Load::Conditional or a combination of both. Here's a simple test script which works for me.

#!/usr/bin/perl

use strict;
use warnings;
use Module::Load;

my $os = 'Yet Unknown';

if ( $^O =~ /MSWin/ ) {
    load 'Win32';
    $os = Win32::GetOSName();
}

print $os;

Output of my test: D:\perl>test.pl
Win7

[sdetweil]

thx.. that works, but I don't understand 'why'.. how does the compiler know NOT to require the Win32 module in this case, but in my existing source, with no explicit use statement it does?

anyhow.. now I have the same problem with TieRegistry <code> use Win32::TieRegistry; $Registry->Open(keyname);

the doc says 'new(keyname)' should work, and then there are a bunch of functions off the handle..

but I get Autoload is deprecated. or open not found.

then must be some easy, clear way to handle this. without having to know the internals of every package.