On Mon, 6 Jul 1998, Rene Brun wrote: > One of the classical problems with existing class libraries > is that objects cannot be made persistent. I understand from your > message that you have an interface for the CLHEP containers. > With your changes, can you embed an Hep3Vector into a class > and write an object of this class? Hm, jes I think so. I just inserted the regular ClassDef and ClassImp macros into the Hep3Vector (and HepLorentzVector) code, so these should behace just like any other root-streamable class. For the HepAList, I had to make up template-aware versions of ClassImp and ClassDef (see my earlier mailing), but now one can have a pointer to a HepAListR (the streamable version of HepAList) in a class and the objects pointed to by the list will be go to a root tree/file. > I would like to hear opinions on the strategy to adapt. > It would probably be interesting to distribute the modified CLHEP > together with the Root binaries (at least in a medium or long term). Yes we could that, but right now it probably needs a bit more testing to make sure its stable. > Meanwhile, I assume that you will provide a Web page documenting > your changes and some examples of use. I will do that, but right now I attend a week-long course and after that is our collaboration meeting, so it will now appear tommorrow. cheers, Stefan ---Stefan Kluth---------------Lynen Fellow----------------|\--|\------- - LBNL, MS 50A 2160 - phone: +1 510 495 2376 - |/ |/ - - 1 Cyclotron Rd. - fax: +1 510 495 2957 - |\/\|\/\|' - ---Berkeley, CA94720, USA-----e-mail: SKluth@lbl.gov------|/\/|/\/|----
This archive was generated by hypermail 2b29 : Tue Jan 04 2000 - 00:34:34 MET