Under Posix compliant operating systems, environment variables are passed in a global associative
array env. The index into env is the name of the
environment variable. The command puts "$env(PATH)" would
print the contents of the PATH environment variable.
:TEXT_END:
:LESSON_TEXT_START_LEVEL 1:
Scripts are much more useful if they can be called with different values
in the command line.
For instance, a script that extracts a particular value from a file could be written so that it prompts for a file name, reads the file name, and then extracts the data. Or, it could be written to loop through as many files as are in the command line, and extract the data from each file, and print the file name and data.
The second method of writing the program can easily be used from other scripts. This makes it more useful.
The number of command line arguments to a Tcl script is passed as the global variable argc. The name of a Tcl script is passed to the script as the global variable argv0, and the rest of the command line arguments are passed as a list in argv.
Another method of passing information to a script is with environment variables. For instance, suppose you are writing a program in which a user provides some sort of comment to go into a record. It would be friendly to allow the user to edit their comments in their favorite editor. If the user has defined an EDITOR environment variable, then you can invoke that editor for them to use.
Under Posix compliant operating systems, environment variables are passed to a Tcl script in a global
associative array env. The index into env is the name of
the environment variable. The command puts "$env(PATH)"
would print the contents of the PATH environment variable.
:TEXT_END:
:LESSON_TEXT_START_LEVEL 2:
There are many ways of getting information from a user into a Tcl script.
For example, the script could:
We've already discussed methods 1 and 2. In this lesson we will discuss methods 3 and 4.
When a program is invoked from a command line, it is invoked with a string of one or more words. Under most operating systems, the first word is the name of the program, and the other words are referred to as the arguments to the program. These arguments can be a file name, (as in cat /etc/passwd) or a flag (as in grep -i foo bar), or a command for the program to execute (as in sed 's/one/two/g'). The interpretation of these words is left up to the program that is being invoked.
You can get the number of command line arguments from the global variable argc. The command line arguments are passed as a list in argv.
A program can even modify its behavior based on the name its invoked as. Sometimes two programs will have most of their of code in common, and just a little bit of different code. In that case, sometimes it's simplest to single program and link copy it into two files with two different names (or use the ln command to link one file to the other name). When this script is run, it should look at the name it was invoked as, and can then choose a particular set of code to execute depending on that name.
The name of a Tcl script is passed to the script as the global variable argv0.
There are also certain pieces of information that a computer user wants to set once, and let any program that needs to know this information find it. These pieces of information are handled with environment variables, and are commonly set in your .profile or .login file. For example, most people have their favorite editor named in the EDITOR environment variable. Programs that let a user edit a file can check that variable to see what editor to invoke.
In Tcl, these environment variables are passed to a script in an associative
array named env. The index into env is the name of the
environment variable your script is checking. To set an editor to invoke
you might write code like:
set editor "vi"
if {[info exists env(EDITOR)]} {set editor $env(EDITOR);}
Now, run the example, and look at the output. In this case, there are no arguments to the script, so argc is 0. If you invoke the script from another command window by typing in the name that is displayed in the second line (/tmp/xm...), you can add arguments to the command line, and see them displayed. :TEXT_END: :CODE_START: puts "There are $argc arguments to this script" puts "The name of this script is $argv0" if {$argc > 0} {puts "The other arguments are: $argv" } puts "You have these environment variables set:" foreach index [array names env] { puts "$index: $env($index)" } :TEXT_END: