Comments

Mava Script comments inside your script to explain the code can be used to make it more readable. Comments are always ended with a closing tag and can span a single or multiple lines.  

Example:

<MvCOMMENT>The code below will output the year.</MvCOMMENT>
<MvEVAL EXPR"{ s.tm_year }">

<MvFUNCTION NAME="Sum" PARAMETERS="var1,var2" STANDARDOUTPUTLEVEL="">
    <MvCOMMENT>
        This function adds two numbers
        Rounded to the neares whole number
    </MvCOMMENT>
    <MvFUNCTIONRETURN VALUE="{ (l.var1 + l.var2) ROUND 0 }">
</MvFUNCTION>

The contents of a comment are ignored by the compiler and not passed on to the browser, so a they are also used when, debugging, and testing your program. By surround a block of code with comments, you may be able to isolate and locate the section with a problems. 

Example:

<MvFUNCTION NAME="Divide" PARAMETERS="var1,var2" STANDARDOUTPUTLEVEL="">
    <MvCOMMENT>
	There is a problem in here somewhere
        <MvFUNCTIONRETURN VALUE="{ l.var1 / 0 }">
    </MvCOMMENT>    
</MvFUNCTION>

You can also use ordinary HTML comments. These are passed to the browser but not displayed. MivaScript within HTML comments are still processed allowing you to embed test script that shows up in the source but not on the display.

Example:

<MIVA STANDARDOUTPUTLEVEL="html, text, compresswhitespace">
<!-- Order_Date = <MvEVAL EXPR"{ g.order_date }"> -->
+ Add a note
User Annotations: comments
Justin Sims : justin at, e-businessexpress d0t com
05/05/2011 19:47 p.m. 
While at first glance the comment tag may appear to be the least powerful, it can certainly prove useful on a regular basis. MvCOMMENT provides a simple method of notating one's code. While performing complex operations or having to take an extended break from coding, I've found that I save a lot of time and frustration by keeping brief notes after every couple of lines or so.

Leaving short but helpful descriptions of what's going on with each major step will save you time down the road when you revisit the source code to make an update or troubleshoot an issue. Additionally, they're also nice for maintaining a changelog inside of your source for version and bugfix tracking.
<MvCOMMENT>
*** Module Changelog ***
   v 5.001   04/11/11   Justin   -Modified query to baskets table to only execute if
                                  g.basket:cust_id is not null
*** Module Changelog ***
</MvCOMMENT>