I do not see how we can synchronise real texttual documentation other by care. For the tests I would like to have information such as: the last time (with a timestamp) the tests were run for this package these ones were ok and those ones not. This way we could have regression data. Same for SmallLint I would like that a package defines the list of rules that make sense to it and may be the expected results. Stef On Sep 27, 2008, at 10:23 AM, Alexandre Bergel wrote:
The idea is nice. But how will you ensure that your meta-data are well synchronized with your code?
Cheers, Alexandre
On 27 Sep 2008, at 09:40, Stéphane Ducasse wrote:
Hi guys
For Moose we started to add package manifesto using DrDoc. We will use the manifesto to document our package with license, documentation, class diagram... Now what I would really like to have is the results of SmallLint rules and the tests because when I run the tests if some of them were broken I do not know whether I made progress or not.
I think that the manifesto could be a nice place to keep such information. After we could have a simple manisfesto dropping script Object allSubclasses do: ....
what do you think about that, I would like to have a bit more self documentation and software engineering meta data within the system.
Stef
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project