Geir Magnusson Jr wrote: > 3) Lock down function and behavior tightly with tests - that if > modified, tests will break, and that should raise an alarm to the > committer.
One easy way would be to add a test that compares the String.java source code with a saved version, and that fails if unequal. This way, any change will trigger a test failure. To get past this failure, one will have to change both String.java and the saved test version. Just an idea... Etienne -- Etienne M. Gagnon, Ph.D. http://www.info2.uqam.ca/~egagnon/ SableVM: http://www.sablevm.org/ SableCC: http://www.sablecc.org/
signature.asc
Description: OpenPGP digital signature
