ChangeSorter: bug or feature?

frits.swinkels frits.swinkels at shaw.ca
Thu Jan 22 04:11:45 UTC 2004


I loaded a changeset from an outside source and did some work in it. I
then loaded a later changeset in which the outside source had done
some more work: I loaded this changeset under a different name. I wanted
to compare the two changesets in a DualChangeSorter. To my
surprise both panes showed the same new source code for methods of the
same name (and class), i.e. my work was wiped out.

On further inspection I noted that the changesets themselves (as opposed
to the sorter which is a view on a changeset) point at the right code,
i.e. the changeset knows precisely which version of a method it
contains. It is the Sorter which goes out and gets the currently loaded
code, whatever that is.

Am I missing a point here? Any suggestions for comparing two changesets
for methods with the same name but different implementations? I can hear
Avi answering Monticello, but I find the Changeset behaviour
counter-intuitive.







More information about the Squeak-dev mailing list