Variable naming rules

ColdFusion variable names, including form field names and custom function and ColdFusion component argument names, must conform to Java naming rules and the following guidelines:

A variable name must begin with a letter, underscore, or Unicode currency symbol.

The initial character can by followed by any number of letters, numbers, underscore characters, and Unicode currency symbols.

A variable name cannot contain spaces.

A query result is a type of variable, so it cannot have the same name as another local variable in the current ColdFusion application page.

ColdFusion variables are not case-sensitive. However, consistent capitalization makes the code easier to read.

When creating a form with fields that are used in a query, match form field names with the corresponding database field names.

Periods separate the components of structure or object names. They also separate a variable scope from the variable name. You cannot use periods in simple variable names, with the exception of variables in the Cookie and Client scopes. For more information on using periods, see Using periods in variable references.

The following rule applies to variable names, but does not apply to form field and argument names:

Prefix each variable's name with its scope. Although some ColdFusion programmers do not use the Variables prefix for local variable names, you should use prefixes for all other scopes. Using scope prefixes makes variable names clearer and increases code efficiency. In many cases, you must prefix the scope. For more information, see About scopes.

Note: In some cases, when you use an existing variable name, you must enclose it with pound signs (#) to allow ColdFusion to distinguish it from string or HTML text, and to insert its value, as opposed to its name. For more information, see Using pound signs.

Version 6.1

Comments are no longer accepted for ColdFusion MX 6.1. ColdFusion 8 is the current version.

Comments

Jedi Master said on Feb 29, 2004 at 6:49 PM :

"A query result is a type of variable, so it cannot have the same name as another local variable in the current ColdFusion application page."

This is not true. You can give a query the same name as an existing variable, however it just overwrites the variable.

toniu27 said on Jun 29, 2004 at 10:03 AM :

"A variable name must begin with a letter, underscore, or Unicode currency symbol"

But why Form.1 works fine?

DracTK said on Jun 15, 2005 at 8:06 PM :

url.1 and form.1 work b/c CF want to be able to work with outside sources of data that may have different variable naming conventions.

Current page: http://livedocs.adobe.com/coldfusion/6.1/htmldocs/variabl3.htm


Contents > Developing ColdFusion MX Applications > Using ColdFusion Variables > Creating variables > Variable naming rules