RE: #pragma link C++ macro ...

From: Philippe Canal <pcanal_at_fnal.gov>
Date: Wed, 02 Mar 2005 13:52:29 -0600

> G__add_macro("MYMACRO", "Expanded Macro");
Is done via

        G__add_macro("MYMACRO=Expanded Macro");

> There is a note in the CINT "reference manual" that "cint handles constant
> value macro as global variable." Maybe that is why in simple cases this
> trick with "global" works.

Indeed. The CINT macro system is unlikely to support your case.

However, all you need to do is

        gROOT->ProcessLine("G__CINT_ENDL G4endl;");

Cheers,
Philippe.

-----Original Message-----
From: owner-roottalk_at_pcroot.cern.ch [mailto:owner-roottalk_at_pcroot.cern.ch] On Behalf Of Jacek M. Holeczek
Sent: Wednesday, March 02, 2005 6:26 AM
To: RootTalk
Cc: 'Masaharu Goto'
Subject: RE: [ROOT] #pragma link C++ macro ...

Hi,

> > if I define the macro there it should still be visible).
>
> Yes this is true but only in ROOT 4.03/02 and later.

I did try it with 4.03/02.
It did not see/register macros defined in the LinkDef file.

> > Anyhow, is there any magic function call that registers a macro?
>
> G__add_macro("MYMACRO");

Thanks, but that is not really sufficient ... I would need a call that actually "adds" the macro and "defines" it ...

        G__add_macro("MYMACRO", "Expanded Macro");

Well, I have almost found a solution ... I am putting one line in my .cxx file which then is precompiled into a shared library ... (this line is then executed automatically during loading of the shared library ...)

----------------------------------------- ProcessLine
static int a_completely_irrelevant_variable = (
       gROOT->ProcessLine("{#define G4endl std::endl}",

&a_completely_irrelevant_variable), 0);

 root [0] .L ./G4.so

• Break *** segmentation violation Generating stack trace... 0x00b3ae07 in G__exec_tempfile_core + 0x1a6 from /.../v4.03.02/lib/libCint.so 0x00b3b10c in G__exec_tempfile_fp + 0x22 from /.../v4.03.02/lib/libCint.so 0x00ba8c3c in G__process_cmd + 0x45ed from /.../v4.03.02/lib/libCint.so 0x002a7c41 in TCint::ProcessLine(char const*, TInterpreter::EErrorCode*) + 0xa9 from /.../v4.03.02/lib/libCore.so 0x00206905 in TApplication::ProcessLine(char const*, bool, int*) + 0x66b from /.../v4.03.02/lib/libCore.so 0x0025ccc8 in TROOT::ProcessLine(char const*, int*) + 0x76 from /.../v4.03.02/lib/libCore.so 0x07080a83 in <unknown> from /.../G4/././G4.so ... ----------------------------------------- G__exec_text static int a_completely_irrelevant_variable = ( G__exec_text("{#define G4endl std::endl}"), 0);

 root [0] .L ./G4.so

• Break *** segmentation violation Generating stack trace... 0x0017ce07 in G__exec_tempfile_core + 0x1a6 from /.../v4.03.02/lib/libCint.so 0x0017d10c in G__exec_tempfile_fp + 0x22 from /.../v4.03.02/lib/libCint.so 0x0017d4bf in G__exec_text + 0x37b from /.../v4.03.02/lib/libCint.so 0x01219a46 in <unknown> from /.../G4/././G4.so ... ----------------------------------------- G__load_text static int a_completely_irrelevant_variable = ( G__load_text("#define G4endl std::endl"), 0);

 root [0] .L ./G4.so
 root [1] .macro
 ...
 #define G4endl 156145856
 ...
 root [2] std::endl
 (class G__CINT_ENDL)156145856

---

Note that ... "G__load_text" registers the macro, but ... it also changes the "std::endl" into an address ...
I would need it to stay "std::endl" ...

Any hints?

> > Also the correct syntax is
> > #pragma link MACRO ZZZ;
>
> This above syntax is indeed wrong.
> Interestingly enough the right syntax is actually:
>
> #pragma link C++ global ZZZ;

There is a note in the CINT "reference manual" that "cint handles constant value macro as global variable." Maybe that is why in simple cases this trick with "global" works.

Thanks in advance,
Best regards,
Jacek. Received on Wed Mar 02 2005 - 21:09:36 MET