Squeak in IEEE Software

Jerome Garcia Jerome.Garcia at wj.com
Tue Feb 2 00:21:50 UTC 1999


     
At 2/1/99 11:05 PM John Brant wrote:
>
A good percentage of the code could be recognized. There would probably be 
3-4 common ways of doing it that would catch 95% of all cases. The 
Smalllint tool from the Refactoring Browser doesn't catch the case above 
(since #streamContents: doesn't exist in VA or VW), but it catches many 
other ones: using do: instead of #collect: or #select:, using #whileTrue: 
instead of #to:do:, using #ifTrue:ifFalse: instead of #min: or #max:, etc. 
Overall, there are over 60 different checks that Smalllint performs and 
many of them are the "grammar" type checks as above. The complete list of 
checks is at:
    http://st-www.cs.uiuc.edu/~brant/RefactoringBrowser/LintChecks.html
>
     
     Thanks for the pointer to LintChecks and the good news. It seems one should 
     then be able to extend such a tool to provide suggestions for the naive. 
     When writing code, it would be nice to be able to get a popup menu or 
     something that would lead me right to the sample of code that I need at the 
     moment. I am thinking of something like an interactive version of an 
     identification key such as the great one in "All That the Rain Promises, 
     and More ... : A Hip Pocket Guide to Western Mushrooms" by David Arora. I 
     mention it simply because it makes a sometimes difficult search process so 
     much easier.
     
     Jerome





More information about the Squeak-dev mailing list