Conventions

only for RuBoard - do not distribute or recompile

The following typographical conventions are used in this book:

Monospaced font indicates Web sites, hostnames, filenames, directory names, commands, and options. Italicized font indicates where you should substitute a value of your own choosing.

Where commands are shown as you enter them, bold indicates the part you type. Non-bold indicates output from the computer. In the following table, the prompt indicates how the command is run:

%	Command is run as a regular UNIX user
#	Command is run as the root UNIX user
C:\>	Command is run under Windows
mysql>	Command is run from the mysql program

In SQL statements, SQL keywords and function names are written in uppercase. Database, table, and column names are written in lowercase. When a SQL statement is shown with a mysql> prompt to indicate that you should run it from the mysql program, it is terminated with a semicolon ; because that is mysql s convention for detecting ends of statements. When a SQL statement is not shown with the mysql> prompt, no assumption is made about how you might issue it, so no semicolon is shown. If you do happen to run the statement from mysql, be sure to add the terminating semicolon.

Where there s something worth noting or some additional information that adds something to the discussion, I ll add a sidebar, which looks like this:

If You Are Not Using mod_perl

You should know one thing about this chapter even if you decide to skip it for now: Most of the rest of this book assumes you ll run your scripts under mod_perl. You can recognize such scripts, because they ll be located in the cgi-perl directory, not in cgi-bin. To use any such script in standalone fashion (assuming it doesn t require mod_perl, of course), just put it in your cgi-bin directory and adjust the URL accordingly.

only for RuBoard - do not distribute or recompile