06-08-2006, 01:52 PM
Mixing therms. Read my prev post, we are having two different conversations here which are not related.
1.- Learning C before C++ is good?
and
2.- Proper OOP.
My points fo view:
1.- Yes 'cause it's good to understand how stuff works.
2.- C++ is not good for learning OOP. It's good when you know OOP.
You missed my point. I was trying to explain the main differences between OOP and procedural. Nothing else. And that was just an example. Don't discuss for the sake of it
1.- Learning C before C++ is good?
and
2.- Proper OOP.
My points fo view:
1.- Yes 'cause it's good to understand how stuff works.
2.- C++ is not good for learning OOP. It's good when you know OOP.
Quote:You're assuming the implementation is exposed. If you only had a listCreate that returned some form of handle, you now are forced to use listGet and listPut. Is C bad because it let's you - like C++ - create an 'unsafe' level of encapsulation ?
You missed my point. I was trying to explain the main differences between OOP and procedural. Nothing else. And that was just an example. Don't discuss for the sake of it
SCUMM (the band) on Myspace!
ComputerEmuzone Games Studio
underBASIC, homegrown musicians
[img]http://www.ojodepez-fanzine.net/almacen/yoghourtslover.png[/i
ComputerEmuzone Games Studio
underBASIC, homegrown musicians
[img]http://www.ojodepez-fanzine.net/almacen/yoghourtslover.png[/i