I think one of the problems with a C++ framework for the PalmOS is the
inability to access globals in some circumstances. If you had a framework
from which you derived subclasses for forms or other objects, and that
framework required virtual functions (which it almost certainly would in
order to abstract out base classes from derived classes), then you run into
difficulties with the framework operating from launch codes that don't have
globals available.
Let's fix that problem first!
As you write more and more Palm applications, you develop modules that can
be reused, in whole, in other projects. If you write these modules with the
same consideration for encapsulation and data hiding that C++ gives you,
they are pretty useful and loosely coupled to the programs in which they are
used (they are good objects).
C++ is not going to solve all your problems, but good OO design (even with a
C implementation [and, yes it can be done, though some things are a bit more
painful]) will help you out quite a bit.
My $0.02.
Kevin
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 21, 1999 5:58 PM
> To: [EMAIL PROTECTED]
> Subject: Re: C++ SDK wanted!
>
>
>
>
> >Still no match for classes...
>
>
> Why not? Let's not get into an "Is too!" "Is not!" kind of
> argument. Support
> your statements.
>
>
> >why common.cpp if it's c code?
>
>
> I didn't say it was C code. I'm just trying to counter your
> (implied) argument
> that you can't write re-usable modules when the Palm OS API
> is described in C.
>
>
> -- Keith
>
>
>
