When programming we surely need to check what it's been done. It's better to verify the code when still in production, during the so-called test period. When published, a web site could still contain errors, but what we surely need to avoid is those annoying syntax errors.
There are specific programs freely available that we can use to do so. Here we are going to see 3 tools that we should carefully consider.
a problem, it returns a message describing the problem and an approximate
location within the source. The problem is not necessarily a syntax error,
although it often is. JSLint looks at some style conventions
as well as structural problems. It does not prove that your program is
As you can see it's quite a complete tool. It's obvious that there's no program that will say if a snippet is correct or not. What those tools can do is help us in spotting a possible issue. And maybe keep our code clean.
Just visit JSLint web page and read for yourself what it can do for us.
JSHint is in some way a more simple tool. First of all is an on-line tool and it ".. is a tool to detect
We just need to put the code, select what kind of checks we need and wait for results.
Again, visit the above web site for more information.
The last tool is a bit different...
automatically generating template-formatted, multi-page HTML (or XML,
The web site explains everything about it and it's worth visiting it, as we all know how important code documentation is (especially in large project).
Ok, folks... that's all for today.