Cool, thanks for replying. The best thing is always if you can reduce the problem to its simplest example; this may mean writing a new, small script to show your issue. People want to be able to copy your sample code right into a file on their computer, run it as is, see the error, make some changes and implement a fix, and post that back here. It's more difficult to help when you can only think about the problem in abstract terms.

For example, now that you've posted your object constructor, I wonder whether you need to construct an object at all. You mention inheritance in a comment, but your code looks like a standalone program. Is there a reason why your code doesn't simply call subroutines as it moves through its flow? Why do you think you need to make this code OO?

As an aside, the constructor for an object usually looks more like this:

sub new {
  my $class = shift;
  my %args  = @_;
  my $self  = {};

  # validate the args

  # do stuff to populate $self

  bless $self, $class;
  return $self;
}
[download]

Hope this helps!