| Purpose: | Create, modify, delete, or display library functions |
| Format: | LIBRARY [/D func /F [func] /P /R file /U] |
| /D | Delete a function (the function name can contain wildcards) |
| /F | Display the loaded (matching) functions (the function name can contain wildcards) |
| /P | Pause after each page when displaying functions |
| /R | Read a function file |
| /U | Update function (otherwise you will get an error when loading a function that already exists). |
Usage:
LIBRARY will load / display / delete library functions, which are similar to batch files but which are loaded into RAM and can be called as if they are internal commands. Library functions are read from files, with the syntax:
functionname {
command1
command2
...
}
The opening brace { must be on the same line as the function name (separated by a space), and the closing brace } must be on a line by itself.
When TCC starts, it will automatically load any library function files in the LIBRARY subdirectory of the TCC installation directory. You can specify a different location by setting the LibraryDirectory INI directive. You can have any number of functions in a file.
If you do not specify any switches, LIBRARY will display the library function names that match the command line argument(s). If you do not specify any arguments, LIBRARY will display all of the library function names.
Library functions can call aliases, internal or external commands, batch files, or other library functions.
The TCC parser will look for a matching library function name before looking for plugins, internal commands, external commands, or batch files.
The TCC startup option /IL will prevent loading the default library functions (from the Library folder).
