> It doesn't depend upon that compiler hack. That hack provides the > ability to put textual data in as an appendix to a method. It is an > entirely independent facility that could be perhaps better included as a > trait for those that want it.
The version I found in the latest Pharo-Dev images has the compiler hack loaded and depends on it (or the package definitions). > I don't think it is fair to use code critics as an argument. You can't deny that references to variables and classes that do not exist in the system are not a serious bug. > To me it > appears that you have developed all of these tools for your own use. Code Critics is part of the refactoring browser by Don Roberts and John Brant. The refactoring browser is one of the most amazing pieces of Smalltalk code I have ever seen. I am maintaining the code-base in Pharo (and previously in Squeak), because it makes me much more productive in my daily work. Code critics provides a huge set of high quality tests for free that can quickly point out flaws in code. It is not always correct, but it is usually very good to find the problematic parts of a system. >> not implemented anywhere. Of course there is not a single test. > What are you talking about: Sake-Tests. I am sorry. I was not aware of that package. I should have checked online. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
