It's not only that... it's UML, Design Patterns... all the goodies of OOP...
C++ is not only about sintaxis changes... (I know that's not what you meant
but...)
I had the chance of working with the Epoc32 C++ SDK, and although it was painful,
it was because the lack of documentation... but once you get the API, you can make
apps more faster... I have some time working full time with the Palm SDK (some
months)... and still the only code reuse I get is by copy&paste, maybe I got used
to OOP, but having to deal with this kind of things is like being back to
basics...
"Gilbert W. Pilz Jr." wrote:
> At 03:57 PM 9/21/99 -0700, [EMAIL PROTECTED] wrote:
> >Just curious...how is a C++ API different from a C API? Since C++ is mostly a
> >superset of C, you can use the current SDK in your C++ programs just fine.
>
> I think Jose may have meant something along the lines of, say, the
> difference between a standard UNIX OS interface and the NEXTSTEP interface.
> So instead of doing something like:
>
> int fd = open(....);
>
> write(fd, *bufp, count);
>
> You would do . . .
>
> File *fileObjp = directoryObj->open(...);
>
> fileObjp->write(*bufp, count);
>
> While this might be nice I don't think its a good idea for Palm at this
> time. The thing is that it is easy enough for developers to create these
> sorts of abstractions on top of the core, procedure-oriented API. Given
> that developers can do this themselves I would have to say that this sort
> of massive reworking of the SDK has to be a lower priority item than all
> the other stuff Palm has on its plate . . .
>
> Gilbert W. Pilz Jr.
> Senior Consulting Engineer
> SeaLion Software, Inc.
> www.clion.com
