Is this a good approach? Presumably you are putting the hashes in the module for a reason, and for that same reason would it not be better to access the hashes from the outside using a subroutine? This would be a first stage towards encapsulation.
I know it sounds like more work, but it will pay off in the long run.For example:
package XYZ;
{
my %Hash1;
my %Hash2;
my %Hash3;
sub populateHashRoutine {
# open the file "raw_file.txt"
open (my $fh, '<', 'raw_file.txt') or die "raw_file: $!";
# Populate %Hash1 %Hash2 %Hash3
while (<$fh>) {
# mumble, mumble, mumble
}
close ($fh);
}
sub GetH1 {
my $key = shift;
return $Hash1{$key}
}
sub GetH2 {
my $key = shift;
return $Hash2{$key}
}
sub GetH3 {
my $key = shift;
return $Hash3{$key}
}
}
1;
#main.pl
#========
use XYZ;
XYZ::populateHashRoutine("raw_file.txt");
#How to print Hash1,Hash2,Hash3 values here ?
print XYZ::GetH1('key1'),"\n";
print XYZ::GetH2('key2'),"\n";
print XYZ::GetH3('key3'),"\n";
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.