• anonymous
When is it a good idea to build a new function for an operation?
MIT 6.00 Intro Computer Science (OCW)
  • Stacey Warren - Expert
Hey! We 've verified this expert answer for you, click below to unlock the details :)
At vero eos et accusamus et iusto odio dignissimos ducimus qui blanditiis praesentium voluptatum deleniti atque corrupti quos dolores et quas molestias excepturi sint occaecati cupiditate non provident, similique sunt in culpa qui officia deserunt mollitia animi, id est laborum et dolorum fuga. Et harum quidem rerum facilis est et expedita distinctio. Nam libero tempore, cum soluta nobis est eligendi optio cumque nihil impedit quo minus id quod maxime placeat facere possimus, omnis voluptas assumenda est, omnis dolor repellendus. Itaque earum rerum hic tenetur a sapiente delectus, ut aut reiciendis voluptatibus maiores alias consequatur aut perferendis doloribus asperiores repellat.
  • schrodinger
I got my questions answered at in under 10 minutes. Go to now for free help!
  • anonymous
As in, "for how small of an operation is it worth building a function?" Does it depend on how many times you're going to use it?
  • shadowfiend
Often yes, it's advised that you write a function as soon as you need something more than once. Modern compilers can generally `inline' code -- meaning that they can detect when a function is relatively short and replace the function call with the code in the function itself, thus removing any performance impact from having `too many' function calls. This is, as usual, something you get a feel for, but small functions are not something to be afraid of. If what it does is not particularly evident, you can move a piece of code into a function so that you can give the function a descriptive name and then when it's used the code is clearer.
  • anonymous

Looking for something else?

Not the answer you are looking for? Search for more explanations.