🚀 go-pugleaf

Amazing isn't it. It's like having to explain why it's a good idea to dring
water out of a glass rather than cupping your hands and scooping.

Simply collecting C functions into C++ methods won't take you where you
want to go in your explanation.

But I think you can get some traction by showing how encapsulating global
data and C functions into a class; creating an interface to that class
through get and set methods; and using an event throwing/handling mechanism
cleans up namespace and spaghetti code.

Next, you can reveal how changes can be made inside the class without
disturbing code which "interfaces" with the class.

I'd hold off on the inheritance and polymorphism stuff until they grasp the
encapsulation stuff.

You also might get better traction on these kind of questions at
alt.comp.lang.c++.moderated. There are some real brains over there.
/Todd


Jeffrey K Regan wrote:

> Can anybody help??
>
> I am in the rather interesting position of having to explain the value
> of object oriented programming to a large corporate architecture team.
> Specifically, I need to explain to them the value of wrapping
> collections of C functions into C++ classes.
>
> Can anybody help me with references that I can use to supplement my own
> explanations? I still cannot believe I am reduced to explaining this
> kind of fundamental thing to a corporate system architecture team. Go
> figure!

--
/Todd Marshall
http://kissinternational.com/~tbm/