CODEWITHSUNDEEP
c#winformsvisual-studio
jsls
jsls

Reputation: 261

Do public class & methods slow down your code?

My teacher ve always said that we shouldn't write the same part of code more than once while programming. But should a code which priority is to be robust & quick use class and methods instead of write down the same code ever and ever?! Does calling a class take a little bit more of time than a direct code?!

For example if i want to do that:

Program1.Action1();
Program1.Action2();
Program1.Action3();
& 
Program2.Action1();

etc etc etc

and I want these actions to be perform the quickest as possible, May I call actions() or write down the full code?!

Adnt his question lead to an another one: For a a project we need to make it easily readable by the teacher so we have a lot of "class tab" on visual studio, we make everything public and we call our class or methods in our mainform.

Ok it's quite organized, very easy to read, BUT doesn't make the code slow down?! Does public "class tab" are slower than a private class in our mainform?! I didn't find anything conlusive anywhere.. Thank you.

Upvotes: 1

Views: 792

Answers (2)

Alberto Chiesa
Alberto Chiesa

Reputation: 7350

You have one main question and some concerns.

Let me address them separately; first: public and private are not, per se, faster or slower. The compiler could, in theory, optimize more when private methods are involved, but I don't think there are many cases when that could make a difference. So, the short answer is NO, public does not slow down your code.

A simple function call has negligible cost. If you're not programming some number-crunchink code looping over and over million and million of times, the cost of some function call is no concern.

So, if you don't have performance problems, you should not care about them. Do yourself a favor, while learning, and write this down 10 times: if you don't have performance problems, you should not care about them.

You should concentrate about code readability and algorithmic complexity, not about micro optimizations which may or may not improve "performance", but can easily complicate the code and create bugs.

Easy to read and test is paramount in (dare I say it?) 98% of the software developed.

Upvotes: 1

Bathsheba
Bathsheba

Reputation: 234715

You could always consider profiling the performance.

But really, you ought to trust that C# will be better than you at making such choices when compiling your code.

The things you state in your question seem like unnecessary micro-optimisations to me that will probably not make a scrap of difference.

Readability and the ability to scale your program are more important considerations: computers are tending to double in speed every year but programmers are getting more and more expensive.

Upvotes: 4

Related Questions