Re: It is not an array!

[premchai21]

My guess is that the object might not be being blessed properly, but without being able to see the Module::Name::new function, there's not much I (we?) can tell about it. Could you post it please?

[hardburn]

This was the constructor:

sub new
{
    my ($class, %parameters) = \@_;

    my $self = bless ({}, ref ($class) || $class);

    return ($self);
}

This came right out of ExtUtils::ModuleMaker. After reading some of the comments in this node, I flipped through the Camel and found this suggestion:

sub new 
{
    my $invocant = shift;
    my $class = ref($invocant) || $invocant;
    my $self = { };
    bless($self, $class);
    return $self;
}

Which appears to me to do basically the same thing (except it's not taking a hashref as a param, which shouldn't matter, and I don't need it anyway). However, the tests all pass with this version.

[premchai21]

I see what is going on now. This line:

my ($class, %parameters) = \@_;

makes a reference to the array @_, and assigns $class that reference. %parameters is left blank. Calling ref on an unblessed array reference returns ARRAY; the next line then blesses $self as ARRAY. Removing the backslash in the first line would cause $class to get the first argument, and %parameters to get the other arguments converted into a hash, which seems to be more what you want.