Why would one want to make everything completely OOP. Wouldn't it slow down the execution big time. Even C++ is slower than C so would C# be even slower? Also, since I come from a C++ background, what is the point of putting main in a class?
Printable View
Why would one want to make everything completely OOP. Wouldn't it slow down the execution big time. Even C++ is slower than C so would C# be even slower? Also, since I come from a C++ background, what is the point of putting main in a class?
>Why would one want to make everything completely OOP.
Software maintainability. Object oriented software is easier to maintain then procedural software. So the costs of maintainment are lower and less time needs to be spend on maintaining the software.
>Wouldn't it slow down the execution big time.
The speed of software doesn't depend very much on the used language, C or C++, but most on the used algorithms.
>Also, since I come from a C++ background, what is the point of
>putting main in a class?
I'm from a C background and having a main as an seperate function looks quite procedural to me. If you want everything to be an object, then there shouldn't be seperate functions. I don't know if that's the true reason, its my personal opinion.
As mentioned OOP has advantages relating to design such as code reusability, integration and testing classes. Many also find that OOP design is more stable than design based on algorithms. Features added to programs cause more substantial loss of form in procedural design as compared to OOP design. It is easier to add and remove OOP components working in an environment that supports encapsulation. It is also easier to refactor OOP programs.
In .net the main fuction is static and like any language serves as the point of entry.
Since everything is an object they are able to use a common type system in .net for all the languages. The langauge semantics offer some uniqueness I hear, but overall they are equivalent, so basicall everything being an object facilitates the goal of having a managed codebase. The framework itself offers a higher level of abstraction and compatibility across languages and platforms.
The are using the .net framework and IL for embedded systems. It's a lightweight version of the framework. The speed of execution is obviously not an issue, but in these embedded systems the real issue has more to do with memory conservation.
C++ is slower than C in only some ways. OOP will no doubt be slower than regular procedural/functional calls just because it causes a bit more of an overhead. If you code in C++ using C syntax(such as using structs only) it can be of the same speed. C# is no doubt going to be slower than C++/C, just look at java. Remember C# is supposed to be cross platform.. so giving up a little bit of speed is one of those things you have to sacrifice.
>C++ is slower than C in only some ways. OOP will no doubt be
>slower than regular procedural/functional calls just because it
>causes a bit more of an overhead.
The only thing that makes OOP "slow" is polymorphism because of the virtual table (and its not really as slow as people like to imagine). Just declaring classes and such is no slower than "normal" function calls.
>Why would one want to make everything completely OOP.
>Wouldn't it slow down the execution big time.
The reason C# and Java are slower is because they're interpreted, not their OOness. The reason C++ code was slower than C had more to do with the language being newer and so the compilers weren't as optimized than it being OO.
>The speed of software doesn't depend very much on the used
>language, C or C++, but most on the used algorithms.
I agree.