Changeset View
Changeset View
Standalone View
Standalone View
EvtGenBase/EvtSimpleRandomEngine.hh
Show All 19 Lines | |||||
#ifndef EVTSIMPLERANDOMENGINE_HH | #ifndef EVTSIMPLERANDOMENGINE_HH | ||||
#define EVTSIMPLERANDOMENGINE_HH | #define EVTSIMPLERANDOMENGINE_HH | ||||
#include "EvtGenBase/EvtRandomEngine.hh" | #include "EvtGenBase/EvtRandomEngine.hh" | ||||
class EvtSimpleRandomEngine : public EvtRandomEngine { | class EvtSimpleRandomEngine : public EvtRandomEngine { | ||||
public: | public: | ||||
EvtSimpleRandomEngine() { _next = 1; } | EvtSimpleRandomEngine() { m_next = 1; } | ||||
void reset() { _next = 1; } | void reset() { m_next = 1; } | ||||
double random() override; | double random() override; | ||||
private: | private: | ||||
unsigned long int _next; | unsigned long int m_next; | ||||
abudinen: Would it make sense to use`size_t` here and in other modifications in this diff? | |||||
Done Inline ActionsWhile I agree that such a change is a good idea, I really prefer to keep the scope of this to the renaming of member variables to the m_-prefix convention and, related to this, fixing all instances of variable shadowing. I will open a Task to keep note of this, however, since there needs generally to be a bit of a standardisation and cleanup of the integer types used in the code. tlatham: While I agree that such a change is a good idea, I really prefer to keep the scope of this to… | |||||
}; | }; | ||||
#endif | #endif |
Would it make sense to use`size_t` here and in other modifications in this diff?