You may find some answers in Coping with Scoping.

That being said, I really think it's a bad idea for your package to try and access variables in main. If a sub in another package needs some information, then pass it to the sub.

One the last line of your test.pl file, what would be the harm in calling your sub like so:

Shop::db_connect( \%conf ) ;
[download]

And then changing your Shop_db_connect function to read:

sub db_connect {
    my $conf = shift ;
    print "Print - ", $conf->{'db_database'},
          " - from the Shop package\n";
}
[download]

I don't know if you are able to access your main varables the way you're trying to, but if you can, you may be leaving the door open for unexpected side effects with your variables in main. If a sub, any sub, needs something that's not supposed to be global, then just give it to it. Don't expect it to come get it itself. If you need the sub to be able to change values you give it, pass them by reference like so:

#! /usr/bin/perl

use strict ;
use Data::Dumper ;

my %conf = ( DB_NAME => 'DB01' ) ;

pass_by_reference( \%conf ) ;

print Dumper( \%conf ) ;

sub pass_by_reference
{
    my $conf = shift ;
    $conf->{DB_NAME} = 'DB03' ;
}
[download]

Even this can be a little messy, because from the calling package there's no way to know what's happening to %conf. But, it's a whole lot cleaner than accessing global variables.

_______________
D a m n D i r t y A p e
Home Node | Email