Tcl Built-In Commands puts(1T)
_________________________________________________________________
NAME
puts - Write to a channel
SYNOPSIS
puts ?-nonewline? ?channelId? string
_________________________________________________________________
DESCRIPTION
Writes the characters given by string to the channel given by channelId. ChannelId must be an identifier for an open channel such as | a Tcl standard channel (stdout or stderr), the return value | from an invocation of open or socket, or the result of a | channel creation command provided by a Tcl extension. The | channel must have been opened for output. If no channelId is specified then it defaults to stdout.Puts normally outputs a newline character after string, but
this feature may be suppressed by specifying the -nonewline
switch.Newline characters in the output are translated by puts to
platform-specific end-of-line sequences according to the
current value of the -translation option for the channel
(for example, on PCs newlines are normally replaced withcarriage-return-linefeed sequences; on Macintoshes newlines
are normally replaced with carriage-returns). See the fcon-
figure manual entry for a discussion on ways in which fcon-
figure will alter output. Tcl buffers output internally, so characters written withputs may not appear immediately on the output file or dev-
ice; Tcl will normally delay output until the buffer is full or the channel is closed. You can force output to appear immediately with the flush command.When the output buffer fills up, the puts command will nor-
mally block until all the buffered data has been acceptedfor output by the operating system. If channelId is in non-
blocking mode then the puts command will not block even if
the operating system cannot accept the data. Instead, Tcl continues to buffer the data and writes it in the background as fast as the underlying file or device can accept it. Theapplication must use the Tcl event loop for nonblocking out-
put to work; otherwise Tcl never finds out that the file or device is ready for more output data. It is possible for anarbitrarily large amount of data to be buffered for a chan-
nel in nonblocking mode, which could consume a large amount Tcl Last change: 7.5 1Tcl Built-In Commands puts(1T)
of memory. To avoid wasting memory, nonblocking I/O should
normally be used in an event-driven fashion with the
fileevent command (don't invoke puts unless you have
recently been notified via a file event that the channel is ready for more output data).EXAMPLES
Write a short message to the console (or wherever stdout is directed):puts "Hello, World!"
Print a message in several parts:puts -nonewline "Hello, "
puts "World!"
Print a message to the standard error channel:puts stderr "Hello, World!"
Append a log message to a file: set chan [open my.log a] set timestamp [clock format [clock seconds]]puts $chan "$timestamp - Hello, World!"
close $chan
SEE ALSO
file(1T), fileevent(1T), Tcl_StandardChannels(3TCL)
KEYWORDS channel, newline, output, writeATTRIBUTES
See attributes(5) for descriptions of the following attri-
butes:_______________________________________
| ATTRIBUTE TYPE | ATTRIBUTE VALUE|
|____________________|__________________|_
| Availability | runtime/tcl-8 |
|____________________|__________________|_
| Interface Stability| Uncommitted ||____________________|_________________|
NOTES Source for Tcl is available on http://opensolaris.org. Tcl Last change: 7.5 2