One thing is that you can pass a reference to a hash instead and then simply replace 
my ($host)=@_; $host="foo";

[download]
with 
my $hash=shift; $hash->{host}="foo";

[download]
Another issue I've found when passing user generated hashes, or hashrefs, as parameters is that its easy to make errors. Just misspell a key name and you've got an error, sometimes one that is hard to track down. So ive found its worth the time to add code to trap incorrect keys. This is nice because similar to drewbies and IraTarballs code it provides defaults as well. Which I find usefull in a constructor, one place where you tend to get named parameter calling conventions. 
package Foo;
use strict;
use Carp;
use Data::Dumper;

my %defaults=( a => "sn",b=>"afu" );

sub test{shift; print "test:",shift,"\n"}
sub test2{&test};
sub new {
    my $class  = shift;
    my $attrs  = shift;
    my %params = @_;
    my $self=bless {%defaults},$class;
    for my $param (keys %params) {
       croak "Unknown param $param"
             unless exists($self->{$param});
       $self->{$param}=$params{$param};
    }
    for my $attr (keys %$attrs) {
       croak "Unknown attribute"
             unless $self->can($attr);
       $self->$attr($attrs->{$attr});
    }
    return $self;
}
my $t=Foo->new( {
                  test=>"Hello",
                  test2=>"There",
                },a=>1,b=>2);
my $tt=Foo->new();
print Dumper $t,$tt;

[download]
It might be a bit long but the point was to show that with perl you have a lot of flexibility in how you can call a subroutine but that it leaves all the errorchecking to you.

Yves
--
You are not ready to use symrefs unless you already know why they are bad. -- tadmc (CLPM)

In reply to Re: passing subroutine arguments directly into a hash by demerphq
in thread passing subroutine arguments directly into a hash by c

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.