Hello Chromatic,

Thanks for your reply. I tried both 'our @ISA' and 'my @ISA' without change to the apparent behavior. Now trying with use parent I am receiving the same results.

What really blows my mind, is when I dump the object itself it shows the correct parameters, when I use the object methods to call the parameters is when I am seeing incorrect results.

With that in mind, could this be what is causing my problems?

# create accessor methods for defined parameters
    for my $datum (keys %{$self}) {
        no strict "refs";
        *$datum = sub {
            shift; # XXX: ignore calling class/object
            $self->{$datum} = shift if @_;
            return $self->{$datum};
        };
    }
[download]

Since this is loaded in the SNMPMonitor::Plugin package, but then inherited to SNMPMonitor::Plugin::Atest (and subsequently Btest) could Btest be overwriting the methods in the symbol table?
After I just typed that I attempted to remove the line :

shift; # XXX: ignore calling class/object
[download]

Even better, (to add to what blows my mind), when I use the methods to access the data I am seeing this bug, when I access the variables directly, I do not have this issue.
...
This must mean that it is an issue with my method of creating accessors for the object, right?

With that in mind, could this be what is causing my problems?

I skimmed that part the first time, but you're right. It's definitely causing you problems. Here's a hint; this is a closure:

*$datum = sub {
   shift; # XXX: ignore calling class/object
   $self->{$datum} = shift if @_;
   return $self->{$datum};
};
[download]

In other words, every time you create a new object, you create a new closure bound to that new $self. Every time you call an accessor or mutator on an existing object, that accessor or mutator uses the values of the most recently created object.

The immediate fix is to look at the XXX comment and make that generated method not close over $self. A better fix overall is not to generate (and clobber previously generated!) accessor and mutator methods in your constructor.

---

Improve your skills with Modern Perl: the free book.

Ok, so what is the recommended way of generating accessor/mutator methods? ^This seems to be the prevailing idiom , and I *really* don't want to code them by hand (or write a program that codes them by hand) since very time I add/remove a parameter I'll have to add/remove the accessor.

My first thought, was to set it so it does not ignor the calling class/object like so:

*$datum = sub {
   my self = shift;
   $self->{$datum} = shift if @_;
   return $self->{$datum};
};
[download]

This didn't work.

Then, I tried doing this without the self:

*$datum = sub {
   $self->{$datum} = shift if @_;
   return $self->{$datum};
};
[download]

Again, no change in result.

Then I tried without the reference to self:

*$datum = sub {
   $datum = shift if @_;
   return $datum;
};
[download]

Surprise, this had no affect either.

Then, I tried doing this without the typeglob. (I'm basically pissing into the wind at this point so what do I have to loose)

$datum = sub {
   my self = shift;
   $self->{$datum} = shift if @_;
   return $self->{$datum};
};
[download]

Not surprisingly, no change again...
Here's what really stumps me, through all of these changes I would expect to see an error at least, but the program behaves *identically* through all of the changes.

The immediate fix is to look at the XXX comment and make that generated method not close over $self.

I guess I don't understand what you mean. How do you reference the object without referencing the object? (Which is what $self is right? a reference to the object.)

really, thank you for all of your help.