Well yes and no.
First using C++ across the interface into the library is out of the
question. You can do that only with OS specific mechanisms and PalmOS
doesn't have any such mechanism. An example is Windows COM.
Also things that result in vtables such virtual functions and certain kinds
of inheritance are out because of the lack of globals.
However if you just use basic C++ features and have a "C" calling interface
into the library you'll be OK. I haven't actually done this, but I have
used C++ to handle launch codes like Find which run in a similarly limited
environment.
LL
At 11:28 AM 12/2/99 -0600, Ray Hsu wrote:
>Hi,
>
>I'm using CodeWarrior to build a shared library. I've used the SampleLib
>project as a starting point. The problem is that I want to use C++ to write
>the shared library. Is this supported?
>
>The problem is that the new and delete operators are linked in from MSL
>Runtime Palm OS (2i).Lib. But when I add MSL Runtime Palm OS (2i).Lib to my
>project, I recieve several link errors of the form:
>
>Link Error : NMWException.cp: 'std::uhandler' has illegal single segment
>32-bit reference to 'std::duhandler()'.
>
>When I change my project type to "PalmOS Application" everything builds.
>But something about using "PalmOS Code Resource" is causing this link error.
>
>Any thoughts would be appreciated,
>Ray
>
