Closed couet closed 3 months ago
@lmoneta : what should we do with that one ? I can modify the code in a way or an other and make a PR, but you should tell me what to do ( !
or not !
). Or we can ignore this issue and I close it.
Sometimes it is persistant ( a ! in the online comment)
Some correction, the !
means transient :) (i.e. most of them are correctly marked as not persistent) and some seems to have already been corrected.
These need to be corrected (///<!
instead of ///<
):
tmva//tmva/inc/TMVA/RuleFitAPI.h:193: mutable MsgLogger fLogger; ///< message logger
tmva//tmva/inc/TMVA/Reader.h:161: mutable MsgLogger* fLogger; ///< message logger
tmva//tmva/inc/TMVA/Config.h:145: mutable MsgLogger* fLogger; ///< message logger
tmva//tmva/inc/TMVA/Types.h:181: mutable MsgLogger* fLogger; ///< message logger
tmva//tmva/inc/TMVA/KDEKernel.h:88: mutable MsgLogger* fLogger; ///< message logger
tmva//tmva/inc/TMVA/PDEFoamKernelBase.h:44: mutable MsgLogger* fLogger; //! message logger
tmva//tmva/inc/TMVA/QuickMVAProbEstimator.h:37: mutable MsgLogger* fLogger;
tmva//tmva/inc/TMVA/OptimizeConfigParameters.h:97: mutable MsgLogger* fLogger; ///< message logger
tmva//tmva/inc/TMVA/LDA.h:78: mutable MsgLogger *fLogger; ///< message logging service
tmva//tmva/inc/TMVA/FitterBase.h:88: mutable MsgLogger* fLogger; // message logger
tmva//tmva/inc/TMVA/ModulekNN.h:163: mutable MsgLogger* fLogger; // message logger
tmva//tmva/inc/TMVA/Timer.h:96: mutable MsgLogger* fLogger; ///< the output logger
tmva//tmva/inc/TMVA/RuleFit.h:173: mutable MsgLogger* fLogger; ///< message logger
tmva//tmva/inc/TMVA/Tools.h:227: mutable MsgLogger* fLogger;
tmva//tmva/inc/TMVA/RuleCut.h:97: mutable MsgLogger* fLogger; // message logger
tmva//tmva/inc/TMVA/ExpectedErrorPruneTool.h:77: mutable MsgLogger* fLogger; ///< message logger
tmva//tmva/inc/TMVA/ROCCalc.h:77: mutable MsgLogger* fLogger; //! message logger
tmva//tmva/inc/TMVA/CostComplexityPruneTool.h:86: mutable MsgLogger* fLogger; //! output stream to save logging information
tmva//tmva/inc/TMVA/GeneticAlgorithm.h:101: mutable MsgLogger* fLogger; // message logger
tmva//tmva/inc/TMVA/VarTransformHandler.h:48: mutable MsgLogger* fLogger; //! message logger
tmva//tmva/inc/TMVA/SimulatedAnnealing.h:118: mutable MsgLogger* fLogger; ///< message logger
tmva//tmva/inc/TMVA/GeneticPopulation.h:99: mutable MsgLogger* fLogger; ///< message logger
These classes are normally never stored in a file, but in case somebody does, there is no reason to store also the MsgLogger, so we can assume that is a transient data member in all cases
In TMVA code the
fLogger
data member appears in several classes. Sometimes it is persistant ( a!
in the online comment) and sometimes it is not. Making a "log message" persistant sounds a bit weird ... But may be it should be ? ... at least the current code is not consistent: