Tcl 8.5命令手册：关键操作与实用函数概览

需积分: 9 79 浏览量更新于2024-07-20 收藏 2.3MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

Tcl 8.5 命令手册是针对 Tcl (Tool Command Language) 8.5版本及其图形界面工具包Tk (Tkinter) 的官方文档。Tcl 是一种强大的脚本语言，广泛应用于系统管理、自动化任务、应用程序开发等领域，尤其在Linux环境下的脚本编写中十分常见。这份手册包含了众多核心命令及其用法，涵盖了基础语法到高级功能。 1. **基本命令**： - `after`: 用于延迟执行指定的命令或操作。 - `error`: 抛出错误并停止程序执行，可用于处理异常情况。 - `lappend`: 追加元素到列表末尾。 - `platform`: 提供操作系统相关的信息。 - `tcl_findLibrary`: 寻找和加载Tcl库函数。 - `append`: 合并两个或多个字符串（或列表）。 2. **数据结构与操作**： - `array`: 创建、操作数组，存储键值对。 - `exit`: 结束当前脚本或程序执行。 - `linsert`: 在列表中插入元素。 - `puts`: 输出信息到标准输出流。 - `tcl_wordBreakAfter` 和 `tcl_wordBreakBefore`: 分割字符串中的单词。 3. **流程控制**： - `auto_execok`: 自动执行某些命令。 - `for`, `while`: 循环结构，执行指定条件下的重复操作。 - `if`, `switch`: 条件判断，根据条件执行不同的代码块。 - `break`, `continue`: 控制循环流程的中断或继续。 4. **文件操作**： - `fileevent`: 监听文件事件。 - `glob`: 扩展文件名匹配，支持通配符。 - `open`, `close`: 打开和关闭文件。 - `read`, `write`: 文件读写操作。 - `rename`: 重命名文件或目录。 5. **字符串处理**： - `concat`: 连接字符串。 - `expr`, `mathfunc`: 表达式计算和数学函数。 - `lrange`, `lreplace`: 字符串子串操作。 - `string`: 提供字符串处理的各种方法，如替换、分割等。 6. **异常处理与调试**： - `catch`: 捕获和处理异常。 - `trace`: 跟踪变量或命令调用。 - `debugger`: 调试工具，用于查看程序运行状态。 7. **系统接口**： - `pid`: 获取或设置进程ID。 - `socket`: 套接字通信，实现网络连接。 - `encoding`, `interp`: 字符编码和解释器管理。 - `package`: 包管理，安装、更新和卸载软件包。 8. **变量与上下文**： - `global`, `local`: 定义变量的作用域。 - `uplevel`: 执行上层作用域中的命令。 - `upvar`: 共享变量和上下文。 9. **交互式特性**： - `cd`: 改变工作目录。 - `gets`: 从输入流读取一行文本。 - `history`: 查看和管理历史命令。 - `source`: 逐行执行外部文件的内容。这份Tcl 8.5 命令手册全面展示了如何利用Tcl进行高效编程，无论是基础操作还是高级功能，都能为开发者提供详细的指导。对于Linux系统上的脚本编写者来说，熟练掌握这些命令将极大地提升工作效率和代码质量。

资源详情

资源推荐

Tcl8.5.19/Tk8.5.19 Documentation > TclCmd > apply

Tcl/Tk Applications | Tcl Commands | Tk Commands | Tcl Library | Tk Library

NAME

apply - Apply an anonymous function

SYNOPSIS

apply func ?arg1 arg2 ...?

DESCRIPTION

The command apply applies the function func to the arguments arg1 arg2 ... and returns the result.

The function func is a two element list {args body} or a three element list {args body namespace} (as if the

list command

had been used). The first element args specifies the formal arguments to func. The specification of the formal arguments

args is shared with the proc command, and is described in detail in the corresponding manual page.

The contents of body are executed by the Tcl interpreter after the local variables corresponding to the formal arguments are

given the values of the actual parameters arg1 arg2 .... When body is being executed, variable names normally refer to local

variables, which are created automatically when referenced and deleted when apply returns. One local variable is

automatically created for each of the function's arguments. Global variables can only be accessed by invoking the global

command or the upvar command. Namespace variables can only be accessed by invoking the variable command or the

upvar command.

The invocation of apply adds a call frame to Tcl's evaluation stack (the stack of frames accessed via uplevel). The execution

of body proceeds in this call frame, in the namespace given by namespace or in the global namespace if none was specified.

If given, namespace is interpreted relative to the global namespace even if its name does not start with “::”.

The semantics of apply can also be described by:

EXAMPLES

This shows how to make a simple general command that applies a transformation to each element of a list.

proc apply {fun args} {

set len [llength $fun]

if {($len < 2) || ($len > 3)} {

error "can't interpret \"$fun\" as anonymous function"

}

lassign $fun argList body ns

set name ::$ns::[getGloballyUniqueName]

set body0 {

rename [lindex [info level 0] 0] {}

}

proc $name $argList ${body0}$body

set code [catch {uplevel 1 $name $args} res opt]

return -options $opt $res

}

proc map {lambda list} {

set result {}

foreach item $list {

lappend result [apply $lambda $item]

}

return $result

}

map {x {return [string length $x]:$x}} {a bb ccc dddd}

→ 1:a 2:bb 3:ccc 4:dddd

map {x {expr {$x**2 + 3*$x - 2}}} {-4 -3 -2 -1 0 1 2 3 4}

-keepnewline

Retains a trailing newline in the pipeline's output. Normally a trailing newline will be deleted.

Marks the end of switches. The argument following this one will be treated as the first arg even if it starts with a -.

If an arg (or pair of args) has one of the forms described below then it is used by exec to control the flow of input and

output among the subprocess(es). Such arguments will not be passed to the subprocess(es). In forms such as “< fileName”,

fileName may either be in a separate argument from “<” or in the same argument with no intervening space (i.e.

“<fileName”).

Separates distinct commands in the pipeline. The standard output of the preceding command will be piped into the

standard input of the next command.

Separates distinct commands in the pipeline. Both standard output and standard error of the preceding command will

be piped into the standard input of the next command. This form of redirection overrides forms such as 2> and >&.

< fileName

The file named by fileName is opened and used as the standard input for the first command in the pipeline.

<@ fileId

FileId must be the identifier for an open file, such as the return value from a previous call to open. It is used as the

standard input for the first command in the pipeline. FileId must have been opened for reading.

<< value

Value is passed to the first command as its standard input.

> fileName

Standard output from the last command is redirected to the file named fileName, overwriting its previous contents.

2> fileName

Standard error from all commands in the pipeline is redirected to the file named fileName, overwriting its previous

contents.

>& fileName

Both standard output from the last command and standard error from all commands are redirected to the file named

fileName, overwriting its previous contents.

>> fileName

Standard output from the last command is redirected to the file named fileName, appending to it rather than

overwriting it.

2>> fileName

Standard error from all commands in the pipeline is redirected to the file named fileName, appending to it rather than

overwriting it.

>>& fileName

Both standard output from the last command and standard error from all commands are redirected to the file named

fileName, appending to it rather than overwriting it.

>@ fileId

FileId must be the identifier for an open file, such as the return value from a previous call to open. Standard output

from the last command is redirected to fileId's file, which must have been opened for writing.

2>@ fileId

FileId must be the identifier for an open file, such as the return value from a previous call to open. Standard error

from all commands in the pipeline is redirected to fileId's file. The file must have been opened for writing.

2>@1

Standard error from all commands in the pipeline is redirected to the command result. This operator is only valid at

the end of the command pipeline.

>&@ fileId

FileId must be the identifier for an open file, such as the return value from a previous call to open. Both standard

output from the last command and standard error from all commands are redirected to fileId's file. The file must have

been opened for writing.

If standard output has not been redirected then the exec command returns the standard output from the last command in

the pipeline, unless “2>@1” was specified, in which case standard error is included as well. If any of the commands in the

pipeline exit abnormally or are killed or suspended, then exec will return an error and the error message will include the

pipeline's output followed by error messages describing the abnormal terminations; the -errorcode return option will contain

additional information about the last abnormal termination encountered. If any of the commands writes to its standard error

file and that standard error is not redirected and -ignorestderr is not specified, then exec will return an error; the error

message will include the pipeline's standard output, followed by messages about abnormal terminations (if any), followed by

the standard error output.

If the last character of the result or error message is a newline then that character is normally deleted from the result or

error message. This is consistent with other Tcl return values, which do not normally end with newlines. However, if -

keepnewline is specified then the trailing newline is retained.

If standard input is not redirected with “<”, “<<” or “<@” then the standard input for the first command in the pipeline is

taken from the application's current standard input.

If the last arg is “&” then the pipeline will be executed in background. In this case the exec command will return a list whose

elements are the process identifiers for all of the subprocesses in the pipeline. The standard output from the last command in

the pipeline will go to the application's standard output if it has not been redirected, and error output from all of the

commands in the pipeline will go to the application's standard error file unless redirected.

The first word in each command is taken as the command name; tilde-substitution is performed on it, and if the result

contains no slashes then the directories in the PATH environment variable are searched for an executable by the given name.

If the name contains a slash then it must refer to an executable reachable from the current directory. No “glob” expansion or

other shell-like substitutions are performed on the arguments to commands.

PORTABILITY ISSUES

Windows (all versions)

Reading from or writing to a socket, using the “@ fileId” notation, does not work. When reading from a socket, a 16-

bit DOS application will hang and a 32-bit application will return immediately with end-of-file. When either type of

application writes to a socket, the information is instead sent to the console, if one is present, or is discarded.

The Tk console text widget does not provide real standard IO capabilities. Under Tk, when redirecting from standard

input, all applications will see an immediate end-of-file; information redirected to standard output or standard error

will be discarded.

Either forward or backward slashes are accepted as path separators for arguments to Tcl commands. When executing

an application, the path name specified for the application may also contain forward or backward slashes as path

separators. Bear in mind, however, that most Windows applications accept arguments with forward slashes only as

option delimiters and backslashes only in paths. Any arguments to an application that specify a path name with

forward slashes will not automatically be converted to use the backslash character. If an argument contains forward

slashes as the path separator, it may or may not be recognized as a path name, depending on the program.

Additionally, when calling a 16-bit DOS or Windows 3.X application, all path names must use the short, cryptic, path

format (e.g., using “applba~1.def” instead of “applbakery.default”), which can be obtained with the “file attributes

fileName -shortname” command.

Two or more forward or backward slashes in a row in a path refer to a network path. For example, a simple

concatenation of the root directory c:/ with a subdirectory /windows/system will yield c://windows/system (two

slashes together), which refers to the mount point called system on the machine called windows (and the c:/ is

ignored), and is not equivalent to c:/windows/system, which describes a directory on the current computer. The

file join command should be used to concatenate path components.

Note that there are two general types of Win32 console applications:

[1]

CLI — CommandLine Interface, simple stdio exchange. netstat.exe for example.

[2]

TUI — Textmode User Interface, any application that accesses the console API for doing such things as cursor

movement, setting text color, detecting key presses and mouse movement, etc. An example would be

telnet.exe from Windows 2000. These types of applications are not common in a windows environment, but do

exist.

剩余327页未读，继续阅读

ygyoe

粉丝: 86
资源: 26

Tcl 8.5命令手册：关键操作与实用函数概览

Tcl解释器-8.5 for windows

ActiveTcl8.4.16.0.282109-win32-ix86-threaded

TCLtools:选择TCL脚本进行Cisco IOS渗透测试

scsi_commands_reference_manual

quectel_ec20_r2.1_at_commands_manual

quectel _ec200x&eg912y&ec600s_ series _ at_commands _ manual

解释Built-in commands

verilog testbench读取tcl

Unknown command 'init-pkill'. Run without commands for usage help.

cmake_minimum_required() should be called prior to this top-level project() call. Please see the cmake-commands(7) manual for usage documentation of both commands.

AC_CONFIG_COMMANDS的作用

kuka active commands inhibited

meson工程生成compile_commands.json

ANSYS Workbench commands

jasper apps command reference manual -- app-specific commands - check_conn

Built-in commands

ModuleNotFoundError: No module named 'speech_commands'

未找到"Commands"选项。

no commands supplied怎么办

RedisCommands有没有什么方法可以删除key

最新资源