> > Why variable numUpdates in PULImpl::mergeUpdateList is declared, assigned > but > > never read? > > Good question :) The easy answer is to just remove it. But I think it can > actually be used to replace the myList.size() in the 2 for loops at lines 1289 > and 1308. Even though new entries can be added in myList during each iteration > of the outer for-loop, I think that during those 2 inner for-loops it is ok to > search myList only up to numUpdates. Do you agree?
Yes I agree, the ops in the other PUL cannot conflict with each other. A conflict must be between one of the operation of the first pul and one of the second pul. -- https://code.launchpad.net/~zorba-coders/zorba/updrevalidate/+merge/79331 Your team Zorba Coders is subscribed to branch lp:zorba. -- Mailing list: https://launchpad.net/~zorba-coders Post to : firstname.lastname@example.org Unsubscribe : https://launchpad.net/~zorba-coders More help : https://help.launchpad.net/ListHelp