34,333
edits
Changes
no edit summary
There is an old saying amongst veteran programmers that goes something like "Don't comment bad code, re-write it!". Before exploring what these seasoned programmers are really saying, it is important to understand what comments are.
Comments in both programming and scripting languages provide a mechanism for the developer to write notes that are ignored by the compiler or interpreter. These notes are intended solely for either the developer or anyone else who may later need to modify the script. The main purpose of comments, therefore, is to allow the developer to make notes that help both anyone who may read the script later to understand issues such as how a particular section of a script works, what a particular function does or what a variable is used to store. Commenting a script is considered to be good practice. Rest assured that a section of script that seems obvious when you write it will often be confusing when you return to it months, or even years later to modify it. By including explanatory comments alongside the script this becomes less of a problem.
Now, back to that old saying - "Don't comment bad code, re-write it!". What this phrase suggests is that if code is well written in the first place you do not need comments to explain what it does and how it does it. It also suggests that if you are having to write lots of comments to explain what a section of your script does then you must have written it badly. Whilst one should always strive to write good code there is absolutely nothing wrong with including comments to explain what the code does. Even a well written script can be difficult to understand if it is solving a difficult problem so, ignore the old programmers adage and never hesitate to comment your JavaScript scripts.
Another useful application of comments in JavaScript is to ''comment out'' sections of a script. Putting comment markers around sections of a script ensures that they are not executed by the interpreter when the web page is loaded. This can be especially useful when you are debugging a script and want to try out something different, but do not want to have to delete the old code until you have tested that the new code actually works.
== Single Line Comments ==
The mechanism for a single line comment borrows from the C++ and Java langauges languages by prefixed the line with //. For example:
<pre>
</pre>
The // syntax tells the intepreter interpreter that everything on the same line following on from the // is a comment and should be ignored. This means that anything on the line before the // comment marker it is ''not'' ignored. The advantage of this is that it enables comments to be placed at the end of a line of scripting. For example:
<pre>
</pre>
In the above example everything after the // marker is considered a comment and, therefore, ignored by the JavaScript interpreter. This is provides an ideal method for placing comments on the same line of script that describe what that particular script line does.
== Multi-line Comments ==
Comments in JavaScript enable the developer to add notes about the script or ''comment out'' sections of script that should not be executed by the interpreter. Comments can be single line comments (using the // marker) or multi-line (beginning with /* and ending with */).
Commenting is considered to be good practice. Regardless of how well you understand the logic of some JavaScript, there is a good chance you may one day have to return to that script and modify it. Often this can be months, or even years, later and what seemed obvious to you at the time you wrote it may seem less obvious in the future. Also, it is often likely that some other person will have to work on your scripts in the future. For both these reasons it is a good idea to provide at least some basic amount of commenting in your scripts.