you mean that it was reverse-engineered to determine the specs for stamp field by looking at it? wow. :)
probably try and error trying to parse all the methods in the system.
Let me clarify, what i proposing.
Entries like:
ADPCMCodec methodsFor: 'private' stamp: 'zz (auto pragmas 12/08) 3/2/2004 07:58'
should look like:
ADPCMCodec methodsFor: 'private' author: 'zz' comment: 'auto pragmas 12/08' timestamp:'3/2/2004 07:58'
and we can leave a potential for future extensions, by taking a message pattern which starts from #methodsFor: ....
and store all keywords which follows it like 'author' 'comment' 'timestamp' in a dictionary, with key/value pairs.
Also, it would be nice to simply evaluate this using smalltalk compiler, but doing a trick with substituting global name bindings like ADPCMCodec with proxies, which understand these messages. Then you will have a clean and extensible changeset/smalltalk source code reader. What could be simpler?
Sounds good and we need to handle not compliant methods. Next question is what do we do for 1.2. Because how can tools relying on time work? Finally point: I have more and more problem to get Timestamp a subclass of DateAndTime. It looks to me like Car inherits from Wheel. Stef