Re: Does the delta editor guarantee that propchangess are precomposed?
On 11/8/05, Malcolm Rowe <firstname.lastname@example.org> wrote:
> Okay, but in order to build the two trees, it has to combine a set of
> revision deltas. Admittedly, it can't stream back the propchanges as it
> iterates through the deltas, because it has to get the content changes
> combined (or at least identified) first, but that's an implementation
> detail that I shouldn't have to know about.
You're certainly right that, if the interface doesn't promise that each
property's value is presented at most once, its clients shouldn't assume
that. I'm glad Philip says that the extant delta producers do actually
follow this rule; it's nicely consistent with the restrictions on the order
in which producers can call the other editor functions. We made those
restrictions to make life easier for delta consumers; hopefully this
restriction will do the same.
Received on Tue Nov 8 23:25:04 2005
This is an archived mail posted to the Subversion Dev