I've seen a couple of submissions to the list recently which had no timestamps in the methods. (Although this has probably always been an occasional problem.)
I think a changeset which includes methods with missing timestamps/initials should be regarded as abnormal... these can get distributed and/or included in the base image, and then you've lost track of when the method was changed (and by who).
One way to partly address this would be to have a warning Confirm dialog appear if you try to file out a changeset which is missing timestamps or initials in any of the to-be-filed-out methods. (It could even prompt for initials at that point and try to add them to the methods. Although it's sometimes true that the person filing out might not have authored the offending methods.)
- Doug Way dway@riskmetrics.com
Bob Arning wrote:
On Thu, 30 Aug 2001 21:00:59 +0200 Henrik Gedenryd ?Henrik.Gedenryd@lucs.lu.se? wrote: ?It appears that Squeak-3.1a doesn't always ask for initials nowadays. I get ?a lot of code with "squeak" as the changer's initials when I work. I'm sorry ?I can't diagnose this any better now, but it may have to do with detecting ?that the image has moved. Has anything changed in the flie system code?
Henrik,
I just tried and it worked for me. One test would be to take an image from which you would expect to see a request for initials and compare (Smalltalk imageName) with the class variable LastImageName in SystemDictionary. The method that should be handling this is SystemDictionary??openSourceFiles.
Cheers, Bob