Parts of this description are "borrowed" from Tcl extension [snit], as the functionality is mostly identical.
In the first form defines an option for instances of this type, and optionally gives it an initial value. The initial value defaults to the empty string if no defaultValue is specified.
An option defined in this way is said to be locally defined. The optionSpec is a list defining the option's name, resource name, and class name, e.g.:
option {-font font Font} {Courier 12}
The option name must begin with a hyphen, and must not contain any upper case letters. The resource name and class name are optional; if not specified, the resource name defaults to the option name, minus the hyphen, and the class name defaults to the resource name with the first letter capitalized. Thus, the following statement is equivalent to the previous example:
option -font {Courier 12}
See The Tk Option Database for more information about resource and class names.
Options are normally set and retrieved using the standard instance methods configure and cget; within instance code (method bodies, etc.), option values are available through the options array:
set myfont $itcl_options(-font)
In the second form you can define option handlers (e.g., -configuremethod), then it should probably use configure and cget to access its options to avoid subtle errors.
The option statement may include the following options:
The named method must take one argument, the option name. For example, this code is equivalent to (though slower than) Itcl's default handling of cget:
option -font -cgetmethod GetOption method GetOption {option} { return $itcl_options($option) }
Note that it's possible for any number of options to share a -cgetmethod.
The named method must take two arguments, the option name and its new value. For example, this code is equivalent to (though slower than) Itcl's default handling of configure:
option -font -configuremethod SetOption method SetOption {option value} { set itcl_options($option) $value }
Note that it's possible for any number of options to share a single -configuremethod.
The named method must take two arguments, the option name and its new value. For example, this code verifies that -flag's value is a valid Boolean value:
option -font -validatemethod CheckBoolean method CheckBoolean {option value} { if {![string is boolean -strict $value]} { error "option $option must have a boolean value." } }
Note that it's possible for any number of options to share a single -validatemethod.