Development #1353: Code cleanup for OCT19
Code cleanup: fles/cosy2018/G__CbmFlibCosy2018Dict.cxx
Cbmroot/OCT19/build/fles/cosy2018/G__CbmFlibCosy2018Dict.cxx:4957:14: warning: declaration shadows a local variable [-Wshadow] int R__i, R__n; ^ Cbmroot/OCT19/build/fles/cosy2018/G__CbmFlibCosy2018Dict.cxx:4934:11: note: previous declaration is here int R__i; ^
Many more instances in the same compile unit.
Updated by Florian Uhlig almost 3 years ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
I fixed the warnings in r14933 by removing some data members from the streamer.
All excluded data members contain a std::vector. The strange thing is that for other data members containing a std::vector no warning appears. In one file there are several data members of type std::vector<TH2*> which do not trigger a compiler warning except one or which does. So I have no clue what is wrong.
I also could not reproduce the compiler warnings on macosx.
A more general question to address here is if we anyway need Streamers for Tasks since we don't save a Task in any file.
Updated by Volker Friese almost 3 years ago
You never know... FairRoot may save some tasks in some parameter file. E.g., to my suprise I realised that CbmUnigenGenerator (used during transport) is instantiated by FairRunAna (in our digitisation run), presumably because it is stored in FairBaseParSet.
But for sure, task members with transient data should not be streamed, such as these vectors that you commented out.