On Sun, 04 May 2008 14:33:10 -0500
"David C. Rankin"
The early 90's is when I was in the thick of things with C++ and OOP with all it's inheritism and polymorphism and other constructs. I'm sure I still have a dozen or so 360k and 1.2M floppies full of old source code. I agree that module should either be in one or the other, but I see so many occasions in many applications where it is nothing but a blend. The hardest thing to get away from is C++ reliance on C functions. There is a lot of old code making use of various string, array, math, etc.. functions that people don't take the time to recode when they need the functionality in a C++ module.
This captures it well:
http://www.3111skyline.com/download/pictures/miscellaneous/software_engineer...
I think I first saw that cartoon back in the 1970s.
But, it tends to be accurate.
Back to C++, use C++ for most everything, and use C stuff only when
there is no C++ alternative. Use the STL also.
--
--
Jerry Feldman