Hi,
I am having a problem building a C++ shared library. The shared library
is a single segment, using the small code model and has 38K of code and 5K
of data. I link with the MSL Runtime Palm OS (2i).lib and am using Code
Warrior R5. I am using the techniques of Ken Krugler to share library
global
Hi,
Well, I can get around this problem by not including the MSL Runtime Palm OS
(2i).lib in my project. However, to do this I have implemented my own
"operator new" and "operator delete" functions where the operator new
function(s) do not throw bad_alloc. My code does not catch new exceptions
but
Patrick,
I'm looking into single-segment C++ development and was wondering if things
have gone well for you since posting your last message or if you've ran into
additional problems. I tried a simple single-segment C++ app and
immediately ran into the problem you discussed -- thanks for the infor
> > Patrick wrote in message <[EMAIL PROTECTED]>...
> > >
> > > [snip]
> > >
> > >I am using the techniques of Ken Krugler to share library
> > >globals.
Where can I find out about these techniques?
DK
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see
>Where can I find out about these techniques?
Handheld Systems published an article with them a few years ago.
There should be a copy in the Palm Knowledge Base.
Regards,
Steve Mann
--
---
Creative Digital Publishing Inc.
1315 Palm Street, San Luis Obisp
> > Patrick wrote in message <14864@palm-dev-forum>...
> > >
> > > [snip]
> > >
> > >I am using the techniques of Ken Krugler to share library
> > >globals.
Where can I find out about these techniques?
DK
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
Patrick,
I'm looking into single-segment C++ development and was wondering if things
have gone well for you since posting your last message or if you've ran into
additional problems. I tried a simple single-segment C++ app and
immediately ran into the problem you discussed -- thanks for the info
Hi,
Well, I can get around this problem by not including the MSL Runtime Palm OS
(2i).lib in my project. However, to do this I have implemented my own
"operator new" and "operator delete" functions where the operator new
function(s) do not throw bad_alloc. My code does not catch new exceptions
but
Hi,
I am having a problem building a C++ shared library. The shared library
is a single segment, using the small code model and has 38K of code and 5K
of data. I link with the MSL Runtime Palm OS (2i).lib and am using Code
Warrior R5. I am using the techniques of Ken Krugler to share library
globa
