{"id":6697,"date":"2022-12-20T19:33:26","date_gmt":"2022-12-20T22:33:26","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/standard-channels-man3\/"},"modified":"2022-12-20T19:33:26","modified_gmt":"2022-12-20T22:33:26","slug":"standard-channels-man3","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/standard-channels-man3\/","title":{"rendered":"Standard Channels (man3)"},"content":{"rendered":"

Standard Channels<\/h1>\n

NAME<\/a>
DESCRIPTION<\/a>
INITIALIZATION OF TCL STANDARD CHANNELS<\/a>
RE-INITIALIZATION OF TCL STANDARD CHANNELS<\/a>
SHELL-SPECIFIC DETAILS<\/a>
SEE ALSO<\/a>
KEYWORDS<\/a> <\/p>\n

\n

______________________________________________________________________________<\/p>\n

NAME <\/a> <\/h2>\n

Tcl_StandardChannels \u2212 How the Tcl library deals with the standard channels ______________________________________________________________________________<\/p>\n

DESCRIPTION <\/a> <\/h2>\n

This page explains the initialization and use of standard channels in the Tcl library.<\/p>\n

The term standard channels<\/i> comes out of the Unix world and refers to the three channels automatically opened by the OS for each new application. They are stdin<\/b>, stdout<\/b> and stderr<\/b>. The first is the standard input an application can read from, the other two refer to writable channels, one for regular output and the other for error messages.<\/p>\n

Tcl generalizes this concept in a cross-platform way and exposes standard channels to the script level.<\/p>\n

APPLICATION PROGRAMMING INTERFACES<\/b>
The public API procedures dealing directly with standard channels are Tcl_GetStdChannel<\/b> and Tcl_SetStdChannel<\/b>. Additional public APIs to consider are Tcl_RegisterChannel<\/b>, Tcl_CreateChannel<\/b> and Tcl_GetChannel<\/b>.<\/p>\n

INITIALIZATION OF TCL STANDARD CHANNELS <\/a> <\/h2>\n

Standard channels are initialized by the Tcl library in three cases: when explicitly requested, when implicitly required before returning channel information, or when implicitly required during registration of a new channel.<\/p>\n

These cases differ in how they handle unavailable platform- specific standard channels. (A channel is not \u201cavailable\u201d if it could not be successfully opened; for example, in a Tcl application run as a Windows NT service.)<\/p>\n\n\n
<\/td>\n\n

1)<\/p>\n<\/td>\n

<\/td>\n\n

A single standard channel is initialized when it is explicitly specified in a call to Tcl_SetStdChannel<\/b>. The states of the other standard channels are unaffected.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

Missing platform-specific standard channels do not matter here. This approach is not available at the script level.<\/p>\n\n\n
<\/td>\n\n

2)<\/p>\n<\/td>\n

<\/td>\n\n

All uninitialized standard channels are initialized to platform-specific default values:<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

(a)<\/p>\n\n\n\n
<\/td>\n<\/td>\n<\/td>\n\n

when open channels are listed with Tcl_GetChannelNames<\/b> (or the file channels<\/b> script command), or<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

(b)<\/p>\n<\/td>\n

<\/td>\n\n

when information about any standard channel is requested with a call to Tcl_GetStdChannel<\/b>, or with a call to Tcl_GetChannel<\/b> which specifies one of the standard names (stdin<\/b>, stdout<\/b> and stderr<\/b>).<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

In case of missing platform-specific standard channels, the Tcl standard channels are considered as initialized and then immediately closed. This means that the first three Tcl channels then opened by the application are designated as the Tcl standard channels.<\/p>\n\n\n
<\/td>\n\n

3)<\/p>\n<\/td>\n

<\/td>\n\n

All uninitialized standard channels are initialized to platform-specific default values when a user-requested channel is registered with Tcl_RegisterChannel<\/b>.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

In case of unavailable platform-specific standard channels the channel whose creation caused the initialization of the Tcl standard channels is made a normal channel. The next three Tcl channels opened by the application are designated as the Tcl standard channels. In other words, of the first four Tcl channels opened by the application the second to fourth are designated as the Tcl standard channels.<\/p>\n

RE-INITIALIZATION OF TCL STANDARD CHANNELS <\/a> <\/h2>\n

Once a Tcl standard channel is initialized through one of the methods above, closing this Tcl standard channel will cause the next call to Tcl_CreateChannel<\/b> to make the new channel the new standard channel, too. If more than one Tcl standard channel was closed Tcl_CreateChannel<\/b> will fill the empty slots in the order stdin<\/b>, stdout<\/b> and stderr<\/b>.<\/p>\n

Tcl_CreateChannel<\/b> will not try to reinitialize an empty slot if that slot was not initialized before. It is this behavior which enables an application to employ method 1 of initialization, i.e. to create and designate their own Tcl standard channels.<\/p>\n

SHELL-SPECIFIC DETAILS <\/a> <\/h2>\n

tclsh<\/b>
The Tcl shell (or rather the function Tcl_Main<\/b>, which forms the core of the shell\u2019s implementation) uses method 2 to initialize the standard channels.<\/p>\n

wish<\/b>
The windowing shell (or rather the function Tk_MainEx<\/b>, which forms the core of the shell\u2019s implementation) uses method 1 to initialize the standard channels (See Tk_InitConsoleChannels<\/b>) on non-Unix platforms. On Unix platforms, Tk_MainEx<\/b> implicitly uses method 2 to initialize the standard channels.<\/p>\n

SEE ALSO <\/a> <\/h2>\n

Tcl_CreateChannel(3), Tcl_RegisterChannel(3), Tcl_GetChannel(3), Tcl_GetStdChannel(3), Tcl_SetStdChannel(3), Tk_InitConsoleChannels(3), tclsh(1), wish(1), Tcl_Main(3), Tk_MainEx(3)<\/p>\n

KEYWORDS <\/a> <\/h2>\n

standard channels<\/p>\n

\n","protected":false},"excerpt":{"rendered":"

Tcl_StandardChannels \u2212 How the Tcl library deals with the standard channels ______________________________________________________________________________ <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2536],"tags":[2538,3007,3075],"class_list":["post-6697","post","type-post","status-publish","format-standard","hentry","category-3-llamadas-de-bibliotecas","tag-2538","tag-man3","tag-tcl_standardchannels"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/6697","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=6697"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/6697\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=6697"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=6697"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=6697"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}