PHP5 Web Hosting - Tomcat EJB Contents

Chapter 3: Using the Basic Building Blocks 61 The Java programming language has three different kinds of comments: Traditional comments: The first five lines of Listing 3-6 form one traditional comment. The comment begins with /*and ends with */. Everything between the opening /*and the closing */is for human eyes only. No information about Java For Dummies or Wiley Publishing, Inc.is translated by the compiler. To read about compilers, see Chapter 2. The second, third, and fourth lines in Listing 3-6 have extra asterisks (*). I call them extra because these asterisks aren t required when you create a comment. They just make the comment look pretty. I include them in Listing 3-6 because, for some reason that I don t entirely understand, most Java programmers add these extra asterisks. End-of-line comments: The text //Changed to I in Listing 3-6 is an end-of-line comment. An end-of-line comment starts with two slashes, and goes to the end of a line of type. Once again, no text inside the end- of-line comment gets translated by the compiler. Javadoc comments: A javadoc comment begins with a slash and two asterisks (/**). Listing 3-6 has two javadoc comments one with text The Displayer class . . .and another with text Execution of the program. . . . A javadoc comment is a special kind of traditional comment. A javadoc comment is meant to be read by people who never even look at the Java code. But that doesn t make sense. How can you see the javadoc comments in Listing 3-6 if you never look at Listing 3-6? Well, a certain program called javadoc (what else?) can find all the javadoc comments in Listing 3-6 and turn these comments into a nice- looking Web page. The page is shown in Figure 3-8. Javadoc comments are great. Here are several great things about them: The only person who has to look at a piece of Java code is the programmer who writes the code. Other people who use the code can find out what the code does by viewing the automatically generated Web page. Because other people don t look at the Java code, other people don t make changes to the Java code. (In other words, other people don t introduce errors into the existing Java code.) Because other people don t look at the Java code, other people don t have to decipher the inner workings of the Java code. All these people need to know about the code is what they read in the code s Web page.
Do you want something as professional as you are? Well, we are, but our plans are even better, please check Web Hosting SSH and look why we are the best.

This entry was posted on Monday, November 5th, 2007 at 8:17 am and is filed under Tomcat EJB Blog. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.