TF1::EvalPar constness

ROOT
1

Hi,

Is there a reason why TF1::EvalPar is not const?

Interestingly, TF1::Eval() is const and calls EvalPar internally (by casting this to non-const), suggesting it’s probably safe to treat EvalPar as const?

2

Hi,

EvalPar takes as input the parameter values and then it calls TF1::SetParameters, which is not const. If you are not passing any parameter values, (i.e. you pass a null pointer as second argument, the default case), you can treat then EvalPar as const.

Lorenzo