Hi all

Have you thought to use the Sunit or another samll testing framework to 
write some regression tests or Unit tests for Squeak? These tests could be removed easily 
from the image and also constitutes a natural documentation. 

Since Kent Beck visited us, we are doing that for everything we develop in VW ( that we 
think is fragile) and it gives a really great 
feeling of security and aggresivity to change the code.  

> 
> >I've noticed that Squeak has trouble keeping source code in sync when
> >storing methods with large literal strings embedded in them.  Usually when
> >this happens, I'm forced to abandon the image, or compress the changes file,
> >or perform some other contortion to get the source code back in sync.
> 
> PlayingCard>>imageData has a 16K literal in it, and I have routinely worked with the 
.ST form of FontSets, which can have literals upwards of 50K, with a full span of 0-255 
ascii codes in them.
> 
> As far as we know, the source code machinery has been rock solid for several years but 
it could well be that some recent change has broken the way certain literals are stored.  
We would very much appreciate it if you can provide a simple case where things are happy 
before and not happy afterwards.
> 
> 	- Dan
> 
> PS:  You aren't shipping .changes files around in a manner that could result in other 
than the *exact* same characters being copied, are you?
> 
> 

Stephane DUCASSE (ducasse at iam.unibe.ch) http://www.iam.unibe.ch/~ducasse/
"if you knew today was your last day on earth, what would you do 
different? ... especially if, by doing something different, today 
might not be your last day on earth" Calvin&Hobbes

University of Bern, Institut fuer informatik and Mathematik
IAM-SCG, 10 neubruckstrasse, CH-3012 Bern, Switzerland.