difference between plain C and a full object oriented programming

[mihai]

I wander what is the penalty of speend for using object oriented
programming (C++) against the play C.

Have a nice day,
Mihai

 

[Rapscallion]

I wander what is the penalty of speend for using object oriented
programming (C++) against the play C.

No, the penalty of speend is always caused by the programmer. BTW, OO
programming is much harder than procedural programming.

 

[E. Robert Tisdale]

I wonder,
"What is the [performance] penalty
for using object oriented programming (C++)
instead of plain C?"

None.
Object oriented programming
is as good an idea in C as it is in C++.
C++ just makes it easier and more reliable
because it is an object oriented programming language --
it includes direct support for object oriented programming:
1.) encapsulation (actually, data hiding),
2.) inheritance and
3.) run-time polymorphism.

Of course, new C++ programmers create problems for themselves
when they try to use the new language features
in inappropriate situations.
As a rule, you should avoid doing anything in C++
that you wouldn't do in C.

 

[Victor Bazarov]

I wander what is the penalty of speend for using object oriented
programming (C++) against the play C.

None whatsoever.

 

[Peter Julian]

I wander what is the penalty of speend for using object oriented
programming (C++) against the play C.

Have a nice day,
Mihai

Both C and C++ can support OO programming. Consider this. Lets suppose you
have a bunch of classes or types that are related in some way. Who will be
faster? The non-OO language programmer that has to create a container for
each single type or the OO programmer that can use one container to store
all the types, including those derived types not yet created?