> >However, problems still exist with using C++, which you should be > aware of. They include first-segment size, virtual table size, and > exception table size, all of which can grow extremely large. < > > To add a data point, I'll just say that I do all my Palm > programming in C++ > and have never had any problems with the latter two concerns. > First-segment > size needs to be addressed in C programs, too, where I > imagine it's as easy > as with C++ programs. > > C++ is more (and less) than exceptions (which I don't use for > Palm) and > virtual functions (which I use sparingly). An "extremely > large" virtual > function table is not a problem with C++--it's a problem with > using a lot of > virtual functions. :) > > I think there are a lot of folks in the Palm community who > are leery of C++ > due to misconceptions about using certain language features > on a low-memory, > low-speed platform (which, BTW, would kick the butt of the PC > I learned C++ > on). Statements like "problems still exist with using C++" > increase this > suspicion without reason, I feel, when the "problems" really > have nothing to > do with the C++ language as a whole. C++ != exceptions. C++ != large > vtables.
I had no intention of arousing suspicions regarding the use of C++ in Palm OS programming. I was merely pointing out the potential problems that are associated with using C++. Although you may not have experienced these issues, it does not mean that they do not exist. I too agree with you that C++ is a perfectly viable choice for Palm application development. In fact, I would actually prefer to use C++, and it is usually my programming language of choice. However, there are certain limitations imposed by the Palm OS platform itself that can cause potential problems. By the way, I mentioned that virtual and exception tables can grow large, not that they will. -- Vinu Raj Metrowerks Developer Support -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
