Hi Andrei, We are unfortunatly aware of this problem that prevents a real use of the TCut class. The operator ! changes the cut. If you implement the cut as intended, I will offer you a bottle of champagne. Rene Brun Andrei Salnikov wrote: > > Hi all, > > I observe something which surprises me a bit: > > root [166] TCut cut1 = "X>0" > root [167] TCut cut2 = "Y<0" > root [168] TCut cut3 = !cut1 && cut2 > root [169] cut1.Print() > OBJ: TCut CUT !(X>0) > > obviosly, '!cut1' changes the value of cut1 itself. Is it supposed to > be like that? My expectations for such constructs would be not to change > the value of operand. > > Cheers, Andy.
This archive was generated by hypermail 2b29 : Tue Jan 02 2001 - 11:50:19 MET