My issue was the possibility of <-1>ing a null value. I use <-1> plenty of times if i absolutely know that the value is not null or i'm creating a log file.
If i'm appending a set of associated mv'd attributes, i still DCOUNT the controlling one (one with never a null) add 1 and directly replace from there. Just my preference that hasn't hurt me. thanks. ----- Original Message ----- From: "Martin Phillips" <[EMAIL PROTECTED]> To: "U2 Users Discussion List" <[EMAIL PROTECTED]> Sent: Tuesday, February 03, 2004 9:55 AM Subject: Re: [UV] VARIABLE<-1> = "" andBasicCompile"$OPTIONSEXTRA.DELIM"work "consistently" > Mark, > > > ...the use of a MV counter either derived or managed is clearly the best > solution... > > Some interesting performance figures... > > X has 100 fields (I cannot remember how big they were for this test) > > X<-1> = 'A' takes 100 time units > X := @FM : 'A' takes 150 time units > X<101> = 'A' takes 9320 time units > X = X : @FM : 'A' takes 9010 time units > > Perhaps, sometimes, X<-1> is a winner! > > Martin Phillips > Ladybridge Systems > 17b Coldstream Lane, Hardingstone, Northampton NN4 6DB > +44-(0)1604-709200 > > _______________________________________________ > u2-users mailing list > [EMAIL PROTECTED] > http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
