> i think you may be a bit confused as to what OOP is all about?
No, not really
OO means objects that have data and methods. Methods are sent from object to object and the object manipulates it's data.
However, in C++, you have more of a procedural interface.
In C, you write do_something(object);
In C++, this becomes object->do_something();
That's a lot less OO than for example smalltalk...
> what i acctually mean, is that you could have both c++ & C includes, the C ones would form the basis
> for includes for other programming languages
Include files wouldn't be enough... there would have to be a class framework as well...
About the non-standardized way of name mangling and object layout:
Every compiler is free to implement name mangling in any way it sees fit. There is (or better was) no standard. So if the system is using a C++ framework, the system would have to define the name mangling, and all compilers would have to implement that...
That's the problem BeOS has: They have their system interfaces as C++, so you were forced for some time to use the BeOS compiler... There's a gcc variant in the meantime, though...
