on 4/10/00 21:40, Steve Sabram at [EMAIL PROTECTED] wrote:
> So true. I have been involved with two ports of C++ code to the PalmOS
> where this exact problem (implicit construction) was causing
> stack crashes all the time. When one project was complete, I ended up
> writing a report that stated that porting the code to the
> PalmOS took longer than if we wrote code from scratch and only
> referenced the data structures needed that we external to the
> project.
>
> At times, writing platform specific code to complete a project has
> created almost a dogmatic conflict over how it should be done.
> Some clients are not used to working with a box this small and somehow
> they think all computers have infinite memory.
So strange... I have a big C++ code base and it compiles and run perfectly
on Palm OS (as well as on at least 6 other platforms: WinCE, MacOS, Windows,
Linux, Tru64 and Solaris). The app is quite large, not because of C++ but
because the code base is big. The only problem we encounter are memory
problems, again not because of C++ but because of memory requirements from
our application.
I think that well thought-out, carefully designed and well written C++ is as
good on PalmOS as straight C. The only thing we don't do in C++ is the UI.
We do not use RTTI for performance reasons, but do good use of exceptions
and it really proved worthwhile. I think there are no arguments against C++
on PalmOS, except for "bad design" (and in some cases, small projects just
don't need it).
--
Florent Pillet, Software Architect
OPTeWAY S.A., 2881 route des cr�tes, BP. 308
06906 Sophia Antipolis cedex, FRANCE
Phone: +33 4 9295 2613 - Fax: +33 4 9295 2601 - http://www.opteway.com/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
