http://qs321.pair.com?node_id=553800


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

Replies are listed 'Best First'.
Re^2: Mixing OO & non OO code in a module
by jdhedden (Deacon) on Jun 06, 2006 at 16:25 UTC
    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.

    Remember: There's always one more bug.