Cumbersome, yes - but it is good style. If you don't really care about others understanding your code (which you should), you could opt for something like:

sub option {
    my ($self,$arg,$value) = @_;
    return $self->{options}->{$arg} unless $value;
    $self->{options}->{$arg} = $value;
}
[download]

A bit more consise, but at what gain?

For your second question - sounds like you want a hash slice:

my %hash;
@hash{('a'..'d')} = (1..4);
[download]

UPDATE: nope, that is not what you want - see Masem's answer.

UPDATE (about an hour of reflection):

To elaborate more - i would avoid using shift like you do. I have been known to do that from time to time, but it is sheer laziness on my behalf when i do.

For serious code, i really tend to use:

sub foo {
   my ($self) = @_;
}
[download]

in case i need to (and usually do) supply more arguments. There are exceptions, such as default values or attaching comments to each argument, but for the most part....

The other item is lining up data structures correctly:

sub new {
    my ($class) = @_;
    
    my $self = {
        foo     => 'bar',
        bar     => 'maz',
        options => {
            anoption      => 1,
            anotheroption => 'foo',
            option3       => 'barbar',
        },
    };
    
    return bless $self, $class;
}
[download]

A lot easier for the eyes to parse! You can indent pretty much however you want, mine is just one way, but always remain consistent in how you do it.

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
F--F--F--F--F--F--F--F--
(the triplet paradiddle)