Re^2: Object Oriented packages - classes and subroutines

in reply to Re: Object Oriented packages - classes and subroutines
in thread Object Oriented packages - classes and subroutines

If a routine is clearly not related to the object instance ($self), make it a class method (shift off $class, call the method like this: My::Class->whatever() ) instead, because.. You almost certainly will want to override one of them

This is actually really annoying as an interface, because it means that whatever can't be exported. And in my experience, for every time you want to override a class method/function, there are hundreds of times you just want to call one.

Comment on Re^2: Object Oriented packages - classes and subroutines Download Code

Replies are listed 'Best First'.
Re^3: Object Oriented packages - classes and subroutines by jplindstrom (Monsignor) on Oct 06, 2008 at 14:22 UTC
Sorry, I don't get it. Call it like this: `my $whatever = My::Class->whatever();` [download] Is it the verbosity of the class name that bothers you or something else? /J	[reply] [d/l]
Re^4: Object Oriented packages - classes and subroutines by educated_foo (Vicar) on Oct 11, 2008 at 07:07 UTC
Yes, it's the totally unnecessary verbosity that's extremely annoying to get rid of. That doesn't bother you?	[reply]
Re^5: Object Oriented packages - classes and subroutines by jplindstrom (Monsignor) on Oct 12, 2008 at 17:38 UTC
A little. Not very much. And traded off against the consistency and flexibility I mentioned earlier in Re: Object Oriented packages - classes and subroutines, brevity loses out. So while I see your point, I value other things way more. /J	[reply]
Re^6: Object Oriented packages - classes and subroutines by educated_foo (Vicar) on Oct 14, 2008 at 03:42 UTC

In Section Seekers of Perl Wisdom