Re: CINT .L problem

Valery Fine (fine@bnl.gov)
Sun, 16 May 1999 23:35:43 -0400


----- Original Message -----
From: Jacek M. Holeczek <holeczek@us.edu.pl>
To: roottalk <roottalk@hpsalo.cern.ch>
Sent: 16 мая 1999 г. 13:49
Subject: CINT .L problem

> Hi,
> Masa writes :
> > h_x pointer should be initialized by ".L". If it wasn't something is
> > already broken before ".L". The problem does not reproduce on my
machine.
> > The pointer is correctly initialized by ".L".
> After some fights with debugger I think it's NOT possible that the .L
> works the way you write. The direct cause is : the G__prerun is set to 1
> during execution of the G_interpret_func ( see the line 2379 and following
> of the file CINT_ifunc.c ).

[ snip]

> --------------------------------------------------------------------------
----
> The t1.cxx was a one line file :
> --------------------------------------------------------------------------
----
> TH1F *h_tpat= new TH1F();
> --------------------------------------------------------------------------
----
Hello, Jacek.

Did you take in account the ROOT/Cint macro "syntax" ?
In my mimd the "legal" ROOT macro would look as follows:

{ TH1F *h_tpat= new TH1F(); }

The page:

http://root.cern.ch/root/CintInterpreter.html

says:

" .... CINT as Macro Processor ...
. . .

Lets start with a macro containing a simple list of statements
(like the multi command line example given in the previous section).
T h i s t y p e o f m a c r o m u s t s t a r t w i t h
a "{" a n d e n d w i t h a "}".
. . . "

Please correct me,
Valery