This brings to mind the old saying
It is easier to making a correct system run fastStrive first to make your code work correctly, and don't concern yourself with speed at an implementation level until you have a system that works. Choose a design that is appropriate to your performance requirements, then focus on implementing it correctly. If that means a few big methods, use big methods. More likely, you'll find that smaller methods are easier to understand and test. Then profile and tune.
than it is to make a fast system run correctly.
In reply to Re: Method calls expensive??
by dws
in thread Method calls expensive??
by chorg
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |