You can also use sub prototypes to help make things pretty. They'll give you some argument checking capability, and will convert your arrays into refs for you. Here's a simple example:
my @foo = qw(123 456 789);
my @bar = qw(abc def ghi);
sub qux(\@\@*)
{ print join "\t", @_, "\n";
my $foo = shift;
my $bar = shift;
print "foo: ", join "\t", @$foo, "\n";
print $FH "bar: ", join "\t", @$bar, "\n";
}
qux(@foo, @bar, 'STDERR');
print "\n";
print \@foo . "\t" . \@bar;
Applying this to your code, we get something like (notice how clean the subroutine call is):
# the filehandle name must be quoted if you have strict subs enabled.
process(@data,@set_up,$template, 'OUT');
# Process
sub process (\@\@$*) {
my $data_ref = shift();
my $set_up_ref = shift();
my $template = shift; #For unpack
my $FH = shift; # The * gets us a handle reference
foreach my $record (@data) {
--do things--}
}
Check out perlsub's section on prototypes for more info.
Update: Of course protoypes are a bit controversial...
TGI says moo
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.