I would take a mixed, application driven approach. I always have the C++ compiler turned on, even when writing procedure based code. 1. Design the Palm app. Pay close attention to the Palm look and feel in the UI and match the palm application to the limits and strengths of the device. Pay special attention to PalmOS memory: small stack, small heap. 2. Code up the User Interface, AppStart, AppStop and so on in whatever is expedient. For a simple app I often use C style procedures copied and modified from Palm's sample code. 3. If the current app is a good object design, try and use the objects when you can. Should save tons of time. Your only problem might be with stack space. > From: "Palm Developer Forum digest" <[EMAIL PROTECTED]> > Reply-To: "Palm Developer Forum" <[EMAIL PROTECTED]> > Date: Thu, 06 Jul 2000 00:00:12 -0700 > To: "palm-dev-forum digest recipients" <[EMAIL PROTECTED]> > Subject: palm-dev-forum digest: July 05, 2000 > > Subject: C Vs C++ > From: Anne Srinivas <[EMAIL PROTECTED]> > Date: Wed, 05 Jul 2000 14:16:07 +0530 > X-Message-Number: 4 > > I have to port a big app from VC++ to Palm OS. > The application is a mapping app with lots of map data,routing and so > on.... > > I am at a juncture where i have to decide between c and c++. > If u can give me any link/document/description comparing c and c++ i > shall be > very gratefull to u. > > I know that > 1. C++ app takes more memory > 2 .C++ app is slow on palm > > Are there any more reasons why we shouldn't go for c++? > > Thanks in advance > > Regards, -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
