There was a bug in timestamp handling for .changes that looks like it was integrated in #14410. http://code.google.com/p/pharo/issues/detail?id=5461 Without digging further, it looks like this might be the issue with the two items below. I'd try a newer image. Martin On Sat, Mar 31, 2012 at 1:13 PM, Bernardo Ezequiel Contreras <vonbecmann@gmail.com> wrote: [...]
*** MCStWriterTest>>#testClassMethodDefinition ' !MCMockClassA class methodsFor: ''as yet unclassified'' stamp: ''''! one
^ 1! ! ' size = 79
' !MCMockClassA class methodsFor: ''as yet unclassified'' stamp: ''ab 7/7/2003 23:21''! one
^ 1! ! ' size = 96
so they have different size.
*** MCStWriterTest>>#testMethodDefinition ' !MCMockClassA methodsFor: ''numeric'' stamp: ''''! one ^ 1! ! ' size = 60
' !MCMockClassA methodsFor: ''numeric'' stamp: ''cwp 8/2/2003 17:26''! one ^ 1! ! ' size = 78
it's the same case as before [...]