For all java files that you turn in for CS1322 programs, you
must include an "ident box" at the top.  The ident box is 
equivalent to putting your name on your paper.  If you 
fail to include your ident box at the top of a java file, 
you will lose points, just as if you forgot to put your
name on your paper in any other class. What exactly is
an ident box?  Lets look at an example:

/**
 * CS1322: Programming Assignment #0 - Fall 2002
 *
 * <PRE>
 * Class P0Phase3 - A class designed to let me write
 * a few small methods to become comfortable with expressions
 * and casting.
 *
 *
 * Revisions:  1.0  August 26th, 2002
 *                  Created class P0Phase3
 *
 *             1.1  August 27th, 2002
 *                  Corrected errors in code
 *
 *             1.2  August 28th, 2002
 *                  Final testing, fixed minor problems and
 *                  fixed a few formatting issues
 *
 * </PRE>
 *
 * Collaboration statement:
 *   I collaborated with Luke Olbrish (gte927p) and Jon Razza (gte050p)
 *   while working on this assignment. We consulted 
 *   www.java_r_us.com for reference as we worked.
 *
 * @author <A HREF="mailto:gte467n@prism.gatech.edu">Andrew Hilton</A>
 * @version Version 1.2, August 28th, 2002
 */

You may have noticed that the ident box looks like a big 
javadoc comment: it is.  When you javadoc your program, 
the information in your ident box goes into the top of the
generated html file. Now lets look at what each part means.


   CS1322: Programming Assignment #0 - Fall 2002

This line is to identify which assignment your file is for.
It specifies the class (CS1322), the assignment (Programming 
Assignment #0), and the semester (Fall 2002).

   <PRE>
   Class P0Phase3 - A class designed to let me write
   a few small methods to become comfortable with expressions
   and casting.
  
  
   Revisions:  1.0  August 26th, 2002
                   Created class P0Phase3
  
               1.1  August 27th, 2002
                    Corrected errors in code
  
               1.2  August 28th, 2002
                    Final testing, fixed minor problems and
                    fixed a few formatting issues
  
   </PRE>


This section is in <PRE> tags to make it smaller.
It contains a description of the file, as well as its
revision history.  Tracking revisions is a good 
practice to make sure that you turn in the correct
version of your code.  Each revision has the revision
number, the date, and the changes that were made to
the file for that revision.

   Collaboration statement:
     I collaborated with Luke Olbrish (gte927p) and Jon Razza (gte050p)
     while working on this assignment.  We consulted 
     www.java_r_us.com for reference as we worked.

The collaboration statement specifies who you worked with, and
what resources [outside those provided by the class] you used
in doing this assignment.  Failure to have this statement will result
in a ZERO for the assignment.  Note that you do not need to include
TAs, lecturers, the class text book, the class lecture slides, 
the class webpage, or the java API in this statement.  If you worked by
yourself, state that in the collaboration statement.  Be sure to include
names and gtnumbers for each person you worked with on the assignment.

	    
   @author <A HREF="mailto:gte467n@prism.gatech.edu">Andrew Hilton</A>
   @version Version 1.2, August 28th, 2002
  
The @author tag specifies who wrote this file.  
When you put your ident box on a file, replace
the e-mail address with your prism e-mail and replace
the name with your name.  You MUST use your prism
e-mail (not CoC e-mail, hotmail, or any other address).
The @version tag states the current version of the file.
This tag should be updated each time the revision history
is modified.  


