Re: Mixing OO & non OO code in a module

[hv]

in reply to Mixing OO & non OO code in a module

I'd normally make such things class methods - if I don't, I find I'm always forgetting to type My::Class::function(...) instead of My::Class->function(...), and it becomes a lot more convenient if I have the classname in a variable:

  my $class = "My::Class";
  my @coords = $class->look_at(something);

Hugo

[jdhedden]

If your class doesn't get inherited, you can do it both ways using:

sub function
{
    # Allow calling as a subroutine or class method
    shift if ($_[0] eq __PACKAGE__);

    ...
}

If you're doing inheritance, you'd need something more involved, but you get the idea.