RE:cint and RogueWave

Masaharu Goto (MXJ02154@nifty.ne.jp)
Mon, 24 Aug 1998 23:32:00 +0900


Carsten,

>For the C++ analysis package of the CERES/NA45 experiment
>I would like to incorporate different shared libraries into root such that
>one can create instances of library class objects directly in the
>interpreter.
>I followed the recipe of " Adding Your Own Classes to ROOT " and
>"The CINT Dictionary Generator" respectively. However the generation
>of the additional object code for the dictionary did not work for the
>RogueWave class library. (Please find all the relevant sources in
>/afs/cern.ch/user/v/voigt/public/testroot )
>>
>changing to options +P and -p in the rootcint call did not work either.
>
>In a telephone call Rene Brun already explained that this indeed is a
>problem
>of cint with preprocessor statements and nested include files (for Rogue
>Wave it is
>defs.h ( included from timer.h ) containing the STARTWRAP ENDWRAP macro
>which
>simply defines an extern "C" statement.
>Since in our case the other class libraries rely on RW this problem seems
>to be
>similar to the one concerning the STL which was already discussed in the
>root-talk list. Rene Brun stated that it might be possible to make the
>RW macros explicitly known to cint or to invoke a preprocessor instead.

Embeddling non-tribial class library like RogueWave is a heavy work.
We need to discuss how to proceed. I have very little idea about RogueWave
now. Is it template based or OO based?

Masaharu Goto