Dear Philippe Although this may be helpful for root programers, I am not sure if this is a good idea for the following reason: Until now there is a clear rule, that you have to use //! if you want to prevent that an object is saved. People who are reading the header files can see immediately, which objects will not be saved. Now you are introducing exceptions, which make the code less readable. In my opinion it would be better to list all classes that are not savable, in the root manual at the page where //! is explained. However, please regard this as my personal opinion. Best regards Christian _._._._._._._._._._._._._._._._ C.h.i.s.t.i.a.n S.t.r.a.t.o.w.a V.i.e.n.n.a A.u.s.t.r.i.a _._._._._._._._._._._._._._._._ Philippe Canal wrote: >Hi Ondrej, > >We updated the ROOT code in CVS so that you original code would work >properly. I.e. it would __silently__ not save your TIter object. To >__know__ that the TIter object are not saveable you have to look up the >class definition/documentation and notice the statement: > ClassDef(TIter,0); >A few other classes in the ROOT code are not saveable. From now on you will >be able to have data member to those and the system will automatically mark >them as transient. > >Cheers, >Philippe. > > > >
This archive was generated by hypermail 2b29 : Thu Jan 01 2004 - 17:50:16 MET