On 1 October 2012 20:44, Frank Shearar <frank.shearar@gmail.com> wrote:
It's all done for you anyway, in the git commit. Who changed what when, it's all done.
right, but same applies to methods. so why storing method's stamps but not classes? either you consistently do all the turtles way down, or end up with zoo full of alien species, where nobody can tell where are they came from and why :) I don't have a readily available solution of how we can painlessly migrate from stamps -> git commit stamps. Maybe we don't need stamps for classes in the form like methods have it, because maybe one day (especially for fresh projects), we can just git stamps for everything. And, sure thing, it doesn't related to filetree alone, because our development tools and metamodel inside images also lacks this information. But since we're talking about metainformation i wanted to note about that as well, if nobody else noticed that our information about system changes would be incomplete without this.
frank
On 1 October 2012 19:42, Igor Stasenko <siguctua@gmail.com> wrote:
oh, and i forgot the most important thing:
classes should also have a stamp, i.e. author and date (and perhaps mood ;). Because it feels strange to me, that each method has stamp, even class comments has stamp, but not the classes. What if my sole change is adding/removing variable(s) or changing a superclass? This information (like who and when did that) is also very useful in same way as for methods.
Yes, i know that Squeak/Pharo does not support that, not sure about other dialects. But we can do better isn't?
-- Best regards, Igor Stasenko.
-- Best regards, Igor Stasenko.