| Article: |
Seven Low-Cost Ways to Improve Legacy Code | |
| Subject: | JLint | |
| Date: | 2004-04-30 07:56:51 | |
| From: | rasmusmc | |
|
Won't JLint solve many of the strong compiler tool problems without having ot change the compiler you use? |
||
Showing messages 1 through 1 of 1.
-
JLint
2004-04-30 15:34:36 Robert Simmons, Jr. |
[View]



However, whatever tool you use, the most important thing is that it is part of your development process. You should be runnign this tool every time you compile. Tools that are run once a week or once a month often find many things but people dont want to go back and fix things so they are soon neglected. This is one reason I favor the integration of such warnings into compilers.