TGeant3::SetCUTS

Hi vmc team,
I recently upgraded to geant3_vmc version 1-8. I've noticed that the new version of TGeant3::SetCUTS contains a new argument. What was:

   virtual  void  SetCUTS(Float_t cutgam,Float_t cutele,Float_t cutneu,
                          Float_t cuthad,Float_t cutmuo ,Float_t bcute ,
                          Float_t bcutm ,Float_t dcute ,
                          Float_t dcutm ,Float_t ppcutm, Float_t tofmax);

   virtual  void  SetCUTS(Float_t cutgam,Float_t cutele,Float_t cutneu,
                          Float_t cuthad,Float_t cutmuo ,Float_t bcute ,
                          Float_t bcutm ,Float_t dcute ,
                          Float_t dcutm ,Float_t ppcutm, Float_t tofmax, Float_t


			  *gcuts);

to allow the specification of 5 user defined cuts. I'm wondering if this interface can be changed to allow a default argument of null for gcuts, i.e.:

virtual void SetCUTS(Float_t cutgam,Float_t cutele,Float_t cutneu,

                          Float_t cuthad,Float_t cutmuo ,Float_t bcute ,
                          Float_t bcutm ,Float_t dcute ,
                          Float_t dcutm ,Float_t ppcutm, Float_t tofmax, Float_t


			  *gcuts=0);

for backward compatibility, and also if the SetCUTS method can be modified to protect against the case of a null gcuts ptr. Thanks & best regards,
-Sue Received on Sun Nov 04 2007 - 20:14:12 CET