Class comments within .change files are anonymous doits

Lex Spoon lex at cc.gatech.edu
Sun Jan 30 22:11:49 UTC 2000


One easy way to fix this would be to use ANSI SIF as the standard
interchange format, instead of traditional fileouts.  SIF makes
everything quite explicit.  Someone has posted SIF code to this list
before; I don't recall the details.

Lex



Les Tyrrell <tyrrell at canis.uiuc.edu> wrote:
> 
> I've been parsing .change and .source files for all publicly available
> versions of Squeak, and have noticed something that I think ought to
> be corrected for the next release.  If possible, I'll try to come
> up with a fix before then.  It may be very simple, but I've noticed
> a few simple changes to the format of these files that have made
> it more difficult to handle them, and I'd like to avoid introducing
> any other problems.
> 
> Since version 1.30 Class comments have been getting stored in the
> change files as though they were doits.  To an image, this is not
> a problem.  But if you are trying to extract information from these
> change logs, as I am doing, then you are going to have a bit of trouble
> identifying which of those doits are supposed to be class comments,
> and if they are class comments, it is possible that there is no
> information ( or outdated information ) identifying which class the
> comment belongs to.  Prior to 1.30, the class comments were stored
> in the same format as we find in file-outs, and are easily identified.
> 
> There are a few things I can do to filter some of the comments out-
> but what should be an easy task can now only be done with manual
> intervention and educated guessing.  I would also wonder how it would
> be possible to recover the comment after an image crash.
> 
> This problem does not affect the V1 and V2.sources files.
> 
> -les





More information about the Squeak-dev mailing list