Re: CINT Q: parsing type definitions on the fly

From: victor perevoztchikov (perev@mail.phy.ornl.gov)
Date: Tue Jun 17 1997 - 18:05:50 MEST


Rene Brun writes:
 ...
> > 
> > --------------------------------------------------------------------------------
> > 
> >         The question is why interactive type definition does require
> >         `typedef' whereas loading the same type definition from the macro
> >         file does not?
> > 
> 
> When you have multilines input, you should always start by a { and close with a }
> The following will work:
> {
>   struct AA {
>   int ia;
>   };
> }

It is not a solution, the definition of AA in this case disappeared.

root [1] {
end with '}'> struct AA { int ia;};
end with '}'> }
root [2] a AA;
Error: No symbol aAA in current scope  FILE:/var/tmp/baaa001wM LINE:1
*** Interpreter error recovered ***

Victor

-- 
-------------------------------------------------------------------------
Victor M. Perevoztchikov         perev@uther1.phy.ornl.gov  [ US
                                 perev@vxcern.cern.ch       [ CH
                                 perev@mx.ihep.su           [ RUS

Oak Ridge National Laboratory, MS 6374, Oak Ridge, TN 37831 (423-574 5928)
                                                       Fax  (423-576 5780)
University of Tennessee, Knoxville, TN 37996-1200  (secre-at 423-974 3342)
9015 Ten Mile Rd. #209 Knoxville TN 37923                   (423-693 2639)



This archive was generated by hypermail 2b29 : Tue Jan 04 2000 - 00:26:19 MET