Well, I read all the posts I can find about this C vs. C++ issue and decided to "convert" a large (and growing) app that we are developing from C to C++.
(We're using CW 8.3.) I did a minimal conversion of the app (made all the type casts explicit, changed const char arrays to char ptr constants, etc.) and nothing more... I did use a template for getting object pointers, but other than that, no classes (just the same typedef's and struct's from the C version), no exception handling, no nothing. I didn't even load in the Palm glue or standard C++ libraries. BTW this only took a couple of hours. The C source created a 106K program on the emulator and the C++ version was 221K. The C code is fairly space-concious (I wrote my first program in 1969 on a GE timesharing system with about 128K words total memory, so I'm quite used to having limited resources :), using bits for flags instead of words, etc. Is this a reasonable way to estimate the "overhead" of using C++ vs. C in this environment? Or, do I need to go further in the conversion to get a decent picture of the implications of moving to C++? If so, what things need to be made C++ish for the comparison to be "valid"? Also, I'm confused... Where does all the extra "stuff " come from? The exact same runtime libraries are used in both apps. The source code is only minimally different. I'd really like to move new development to C++, but can't do it with this kind of impact. (Please, no flames or religious wars about language choices, etc.) Thanks, Mitch -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
