in reply to Object Oriented packages - classes and subroutines

I vote with Tanktalus: make them methods. I've had too many cases where I went back to refactor things and had to change them to methods, increasing the odds of bugs. I also have had bugs caused by not remembering which ones are methods, so I think it's easier to just be very consistent about it.
  • Comment on Re: Object Oriented packages - classes and subroutines