writing universal code

Dariusz Miskowiec (D.Miskowiec@clri6a.gsi.de)
Fri, 09 Jul 1999 10:17:24 +0200


Dear Rooters,

I have a very basic question. (In fact, I nearly expect an answer
of the kind "Look in the tutorial xxx...") The question is:

How to write code which, without any changes, can be depending
on the actual need 1) interpreted by root, 2) compiled into a
shared library and loaded into root, and possibly 3) compiled
into a stand-alone program?

The include statements that are needed for compilation but
would be disturbing in the interpreted mode can be surrounded by
#ifndef __CINT__ and #endif. Fine. But how about the ClassDef
statement? It is needed for rootcint but disturbing in the
interpreter mode, and it seems that the variable __CINT__ is
set in both these situations.

I would be grateful for an example of such code. Best regards

Dariusz Miskowiec

-- 
+-------------------------------------------------------------------+
+  Dariusz Miskowiec                    E-mail: D.Miskowiec@gsi.de  +
+  GSI, Planckstr. 1                    Phone:  0049-6159-712-133   +
+  D-64291 Darmstadt                    Fax:    0049-6159-712-785   +
+-------------------------------------------------------------------+