Difference between revisions of "Comments in JavaScript"

From Techotopia
Jump to: navigation, search
(Single Line Comments)
(Single Line Comments)
Line 17: Line 17:
  
 
// This is another comment
 
// This is another comment
 +
</pre>
 +
 +
The // syntax tells the intepreter that everything on the same line following on from the // is a comment and should be ignored. This means that anything on the the line before the // comment marker it is ''not'' ignored. The advantage of this is that it enables comments to placed at the end of a line of scripting. For example:
 +
 +
<pre>
 +
 +
var myString = "Welcome to Technotopia"; // Variable containing welcome string
 +
 
</pre>
 
</pre>

Revision as of 15:04, 19 April 2007

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 explain what a section of your script does then you must have written is 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 comment your JavaScript scripts.

Another useful application of comments in JavaScript to comment out sections of a script. By 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 the new code actually works.

Single Line Comments

The mechanism for a single line comment borrows from the C++ and Java langauges by prefixed the line with //. For example:

// This is a comment line. It is for human use only and is ignored by the JavaScript Interpreter.

var myString = "Hello";

// This is another comment

The // syntax tells the intepreter that everything on the same line following on from the // is a comment and should be ignored. This means that anything on the the line before the // comment marker it is not ignored. The advantage of this is that it enables comments to placed at the end of a line of scripting. For example:


var myString = "Welcome to Technotopia"; // Variable containing welcome string