🚀 go-pugleaf

AFAIK, exceptions only work correctly if the CRuntime is initialized
correctly. Just loading your shared library (by the Java Runtime) and
invoking one of the exported functions is not enough. It does not depend
on the version of CW.

You have to see the details about MSL (e.g. see the source files) on how
to do the initialization.

Best bet it to add a function to your library that is called when your
library is loaded (see the linker panel) and do the initialization there.

Happy programming,
Eddy Walet
PTH

PS, I read your other messages also in the thread about the announcement
of the CW8.

  > I can't continue with my
  > work with the lack of functionality I need from CW7.2 on MacOSX...

I cannot imagine there is anything that you cannot do with CWPRO7.2. I
have even used an older version (CW11) to do the work you are describing
and I even used MPW for it.
Reasons to upgrade might be evolving of the languages (e.g. CW11 does
not understand templates in C++), easier use or more up-to-date
installation of related information (header files, libraries or even
targets). Most of these reasons come into existence when you are working
on projects that include several programmers on different platforms (or
only different tools)


-- 
=============================
This mail-address is not valid. It is used to prevent my own address
from being harvested by a bot.
If you want to contact me you can use:
	brockman-AT-xs4all-DOT-nl
Sorry for any inconvenience this may give.
Kent Brockman is not my real name.
=============================

Leon wrote:

   > I forgot to say, C++ compiler and C++ Exceptions are enabled in the
   > TargetSettings preferences panel.
   >