In my experience, the reputed bloat in C++ programming comes from the use and inclusion of high functionality (hence bloated) classes. For example, avoid "cout"! When creating C++ wrappers for Palm OS(tm) API calls, you add little extra code, but get a lot more compile-time validation of your program. My Palm database class hides the weirdness of the creating, opening, closing, writing, deleting, searching, and reading 'files', and places all the necessary low-level code inside the class methods instead of scattering it multiple times within the program. So in this case my programs are smaller as a result of using C++, and the code is more readable and maintainable. But the real benefit I acheived since the database class became stable, and my other API wrappers became stable, is that I stopped getting those nasty memory violation related messages from new code! Roger Stringer Marietta Systems, Inc. ---------------------------------------------------------------------- >Date: 22 Sep 1999 09:47:08 -0700 >From: Richard Hartman <[EMAIL PROTECTED]> >Subject: RE: C++ SDK wanted! >Real programmers don't need UML. Why, when I was >starting out, we had to wrestle the bits to the >ground individually and pin 'em to the memory core >with spare bits of wire! In the snow ... uphill ... >both ways! </sarcasm> >Sure there are advantages to OO design and C++ implementation >... but there are advantages to C and even assembly. One >of the big costs of C++ is the associated overhead. If you >want to buy those advantages at that cost, go for it. As >somebody else said, there may even be a product market out >there for it (but bear in mind that Teenee was there first).
