I think Sue is making a very good point: there is a lot of sense in
splitting of a class like
class Event {
Int_t fEventNumber;
Int_t fNTracks;
TObjArray* fTracks; //
}
into 3 branches: one for event number, one for the number of tracks and the 3rd one
for the tracks. Certainly this can be done by hands - one always can define the branches
himself, however having this autometed would be a great help. In general, it would be
really nice to have an easy way to say that the data of given class member
(fTracks in the example above) SHOULD NOT be split even if the mother branch is written
in split mode.
I suspect that ROOT already has all (or almost all) the necessary infrastructure
to do this. The missing part is a way to tell ROOTCINT that fTracks has to go
into non-split branch no matter what. In principle, some special character following
the comment (for example, `// #') can be used to pass this message, however
TObjArray* fTracks; // *non-split*
looks much more explicit than
TObjArray* fTracks; // #
... but this is already a minor issue...
best, Pasha
This archive was generated by hypermail 2b29 : Tue Jan 01 2002 - 17:50:40 MET