diff options
| author | Steve Bennett <steveb@workware.net.au> | 2010-10-09 08:17:31 +1000 |
|---|---|---|
| committer | Steve Bennett <steveb@workware.net.au> | 2010-10-15 11:02:57 +1000 |
| commit | 3cfb6f5e312305d7641340917a251606efdf4611 (patch) | |
| tree | 44d9ee99f3a57b0c0cbef3252e082a131715c085 | |
| parent | e7beda66d79f1016865c83aad261b5d1558a7187 (diff) | |
| download | jimtcl-3cfb6f5e312305d7641340917a251606efdf4611.zip jimtcl-3cfb6f5e312305d7641340917a251606efdf4611.tar.gz jimtcl-3cfb6f5e312305d7641340917a251606efdf4611.tar.bz2 | |
Add install target to Makefile
This also respects CFLAGS and LDFLAGS from configure
and allows them to be overriden on the make command line
Signed-off-by: Steve Bennett <steveb@workware.net.au>
| -rw-r--r-- | .gitignore | 13 | ||||
| -rw-r--r-- | Makefile.in | 50 | ||||
| -rw-r--r-- | Tcl.html_shipped | 6376 | ||||
| -rwxr-xr-x | configure | 543 | ||||
| -rwxr-xr-x | configure.ac | 77 | ||||
| -rw-r--r-- | jim.h | 2 | ||||
| -rw-r--r-- | jimautoconf.h.in (renamed from autoconf.h.in) | 2 | ||||
| -rw-r--r-- | jimautoconfext.h.in | 2 |
8 files changed, 6840 insertions, 225 deletions
@@ -3,3 +3,16 @@ config.log config.status config.h tags +.clean +Makefile +Tcl.html +jimautoconf.h +jimautoconfext.h +jim-glob.c +jim-stdlib.c +jim-tclcompat.c +jim-tree.c +jimsh +libjim.a +libjim.so +*.o diff --git a/Makefile.in b/Makefile.in index b280621..8425174 100644 --- a/Makefile.in +++ b/Makefile.in @@ -1,36 +1,40 @@ -RANLIB ?= ranlib +# Tools +CC = @CC@ +CROSS ?= @CROSS@ +RANLIB ?= $(CROSS)ranlib +AR ?= $(CROSS)ar # Configuration jim_libtype := @JIM_LIBTYPE@ SH_CFLAGS ?= @SH_CFLAGS@ SH_LDFLAGS ?= @SH_LDFLAGS@ +CFLAGS = @CFLAGS@ +LDFLAGS = @LDFLAGS@ +DESTDIR ?= @prefix@ # Defines the extensions to include EXTENSIONS := @JIM_EXTENSIONS@ # Set an initial, default library and auto_path -CFLAGS += -DTCL_LIBRARY=\"/lib/tcl6\" +CPPFLAGS += -DTCL_LIBRARY=\"/lib/jim\" -CFLAGS += -DJIM_TCL_COMPAT -DJIM_REFERENCES +CPPFLAGS += -DJIM_TCL_COMPAT -DJIM_REFERENCES -CFLAGS += -Wall -g $(OPTIM) -I@SRCDIR@ -I. @EXTRA_CFLAGS@ +CPPFLAGS += -Wall -g $(OPTIM) -I@SRCDIR@ -I. @EXTRA_CFLAGS@ VPATH := @SRCDIR@ ifeq ($(jim_libtype),static) - # Emulate tinytcl - LIBJIM := libtcl6.a + LIBJIM := libjim.a else - LIBJIM := libtcl6.so - CFLAGS += $(SH_CFLAGS) + LIBJIM := libjim.so + CPPFLAGS += $(SH_CFLAGS) endif .EXPORT_ALL_VARIABLES: OBJS := jim-subcmd.o jim-interactive.o jim.o -SDKHDRS := jim.h jim-subcmd.h - EXTENSIONS_OBJS := $(patsubst %,jim-%.o,$(EXTENSIONS)) .PRECIOUS: jim-%.c @@ -47,7 +51,21 @@ all: jimsh docs: Tcl.html jimsh: $(LIBJIM) jimsh.o - $(CC) $(LDFLAGS) -o $@ jimsh.o $(LIBJIM) $(LDLIBS) @LIBDL@ -lm + $(CC) $(CFLAGS) $(LDFLAGS) -o $@ jimsh.o $(LIBJIM) $(LDLIBS) @LIBSOCK@ @LIBDL@ -lm + +install: all docs + install -d $(DESTDIR)/bin + install jimsh $(DESTDIR)/bin + install -d $(DESTDIR)/lib + install $(LIBJIM) $(DESTDIR)/lib + install -d $(DESTDIR)/include + install @SRCDIR@/jim-*.h $(DESTDIR)/include + install jimautoconfext.h $(DESTDIR)/include/jimautoconf.h + install -d $(DESTDIR)/doc/jim + install Tcl.html $(DESTDIR)/doc/jim + +test: + $(MAKE) -C tests ifeq ($(jim_libtype),static) $(LIBJIM): $(OBJS) $(EXTENSIONS_OBJS) @@ -55,16 +73,20 @@ $(LIBJIM): $(OBJS) $(EXTENSIONS_OBJS) $(RANLIB) $@ else $(LIBJIM): $(OBJS) $(EXTENSIONS_OBJS) - $(CC) $(LDFLAGS) $(SH_LDFLAGS) -o $@ $^ + $(CC) $(CFLAGS) $(LDFLAGS) $(SH_LDFLAGS) -o $@ $^ endif Tcl.html: jim_tcl.txt - asciidoc -o $@ -d manpage $^ + asciidoc -o $@ -d manpage $^ || cp @SRCDIR@/Tcl.html_shipped Tcl.html clean: rm -f *.o lib*.a jimsh Tcl.html if [ -f .clean ]; then rm -f `cat .clean` .clean; fi distclean: clean - rm -f autoconf.h Makefile config.status config.log + rm -f jimautoconf.h jimautoconfext.h Makefile config.status config.log rm -rf autom4te.cache + +ship: + cp Tcl.html Tcl.html_shipped + autoconf && autoheader diff --git a/Tcl.html_shipped b/Tcl.html_shipped new file mode 100644 index 0000000..bb4632f --- /dev/null +++ b/Tcl.html_shipped @@ -0,0 +1,6376 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
+ "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<head>
+<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
+<meta name="generator" content="AsciiDoc 8.6.1" />
+<title>Jim Tcl(n)</title>
+<style type="text/css">
+/* Debug borders */
+p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
+/*
+ border: 1px solid red;
+*/
+}
+
+body {
+ margin: 1em 5% 1em 5%;
+}
+
+a {
+ color: blue;
+ text-decoration: underline;
+}
+a:visited {
+ color: fuchsia;
+}
+
+em {
+ font-style: italic;
+ color: navy;
+}
+
+strong {
+ font-weight: bold;
+ color: #083194;
+}
+
+tt {
+ color: navy;
+}
+
+h1, h2, h3, h4, h5, h6 {
+ color: #527bbd;
+ font-family: sans-serif;
+ margin-top: 1.2em;
+ margin-bottom: 0.5em;
+ line-height: 1.3;
+}
+
+h1, h2, h3 {
+ border-bottom: 2px solid silver;
+}
+h2 {
+ padding-top: 0.5em;
+}
+h3 {
+ float: left;
+}
+h3 + * {
+ clear: left;
+}
+
+div.sectionbody {
+ font-family: serif;
+ margin-left: 0;
+}
+
+hr {
+ border: 1px solid silver;
+}
+
+p {
+ margin-top: 0.5em;
+ margin-bottom: 0.5em;
+}
+
+ul, ol, li > p {
+ margin-top: 0;
+}
+
+pre {
+ padding: 0;
+ margin: 0;
+}
+
+span#author {
+ color: #527bbd;
+ font-family: sans-serif;
+ font-weight: bold;
+ font-size: 1.1em;
+}
+span#email {
+}
+span#revnumber, span#revdate, span#revremark {
+ font-family: sans-serif;
+}
+
+div#footer {
+ font-family: sans-serif;
+ font-size: small;
+ border-top: 2px solid silver;
+ padding-top: 0.5em;
+ margin-top: 4.0em;
+}
+div#footer-text {
+ float: left;
+ padding-bottom: 0.5em;
+}
+div#footer-badges {
+ float: right;
+ padding-bottom: 0.5em;
+}
+
+div#preamble {
+ margin-top: 1.5em;
+ margin-bottom: 1.5em;
+}
+div.tableblock, div.imageblock, div.exampleblock, div.verseblock,
+div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
+div.admonitionblock {
+ margin-top: 1.0em;
+ margin-bottom: 1.5em;
+}
+div.admonitionblock {
+ margin-top: 2.0em;
+ margin-bottom: 2.0em;
+ margin-right: 10%;
+ color: #606060;
+}
+
+div.content { /* Block element content. */
+ padding: 0;
+}
+
+/* Block element titles. */
+div.title, caption.title {
+ color: #527bbd;
+ font-family: sans-serif;
+ font-weight: bold;
+ text-align: left;
+ margin-top: 1.0em;
+ margin-bottom: 0.5em;
+}
+div.title + * {
+ margin-top: 0;
+}
+
+td div.title:first-child {
+ margin-top: 0.0em;
+}
+div.content div.title:first-child {
+ margin-top: 0.0em;
+}
+div.content + div.title {
+ margin-top: 0.0em;
+}
+
+div.sidebarblock > div.content {
+ background: #ffffee;
+ border: 1px solid silver;
+ padding: 0.5em;
+}
+
+div.listingblock > div.content {
+ border: 1px solid silver;
+ background: #f4f4f4;
+ padding: 0.5em;
+}
+
+div.quoteblock, div.verseblock {
+ padding-left: 1.0em;
+ margin-left: 1.0em;
+ margin-right: 10%;
+ border-left: 5px solid #dddddd;
+ color: #777777;
+}
+
+div.quoteblock > div.attribution {
+ padding-top: 0.5em;
+ text-align: right;
+}
+
+div.verseblock > pre.content {
+ font-family: inherit;
+}
+div.verseblock > div.attribution {
+ padding-top: 0.75em;
+ text-align: left;
+}
+/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
+div.verseblock + div.attribution {
+ text-align: left;
+}
+
+div.admonitionblock .icon {
+ vertical-align: top;
+ font-size: 1.1em;
+ font-weight: bold;
+ text-decoration: underline;
+ color: #527bbd;
+ padding-right: 0.5em;
+}
+div.admonitionblock td.content {
+ padding-left: 0.5em;
+ border-left: 3px solid #dddddd;
+}
+
+div.exampleblock > div.content {
+ border-left: 3px solid #dddddd;
+ padding-left: 0.5em;
+}
+
+div.imageblock div.content { padding-left: 0; }
+span.image img { border-style: none; }
+a.image:visited { color: white; }
+
+dl {
+ margin-top: 0.8em;
+ margin-bottom: 0.8em;
+}
+dt {
+ margin-top: 0.5em;
+ margin-bottom: 0;
+ font-style: normal;
+ color: navy;
+}
+dd > *:first-child {
+ margin-top: 0.1em;
+}
+
+ul, ol {
+ list-style-position: outside;
+}
+ol.arabic {
+ list-style-type: decimal;
+}
+ol.loweralpha {
+ list-style-type: lower-alpha;
+}
+ol.upperalpha {
+ list-style-type: upper-alpha;
+}
+ol.lowerroman {
+ list-style-type: lower-roman;
+}
+ol.upperroman {
+ list-style-type: upper-roman;
+}
+
+div.compact ul, div.compact ol,
+div.compact p, div.compact p,
+div.compact div, div.compact div {
+ margin-top: 0.1em;
+ margin-bottom: 0.1em;
+}
+
+div.tableblock > table {
+ border: 3px solid #527bbd;
+}
+thead, p.table.header {
+ font-family: sans-serif;
+ font-weight: bold;
+ color: #527bbd;
+}
+tfoot {
+ font-weight: bold;
+}
+td > div.verse {
+ white-space: pre;
+}
+p.table {
+ margin-top: 0;
+}
+/* Because the table frame attribute is overriden by CSS in most browsers. */
+div.tableblock > table[frame="void"] {
+ border-style: none;
+}
+div.tableblock > table[frame="hsides"] {
+ border-left-style: none;
+ border-right-style: none;
+}
+div.tableblock > table[frame="vsides"] {
+ border-top-style: none;
+ border-bottom-style: none;
+}
+
+
+div.hdlist {
+ margin-top: 0.8em;
+ margin-bottom: 0.8em;
+}
+div.hdlist tr {
+ padding-bottom: 15px;
+}
+dt.hdlist1.strong, td.hdlist1.strong {
+ font-weight: bold;
+}
+td.hdlist1 {
+ vertical-align: top;
+ font-style: normal;
+ padding-right: 0.8em;
+ color: navy;
+}
+td.hdlist2 {
+ vertical-align: top;
+}
+div.hdlist.compact tr {
+ margin: 0;
+ padding-bottom: 0;
+}
+
+.comment {
+ background: yellow;
+}
+
+.footnote, .footnoteref {
+ font-size: 0.8em;
+}
+
+span.footnote, span.footnoteref {
+ vertical-align: super;
+}
+
+#footnotes {
+ margin: 20px 0 20px 0;
+ padding: 7px 0 0 0;
+}
+
+#footnotes div.footnote {
+ margin: 0 0 5px 0;
+}
+
+#footnotes hr {
+ border: none;
+ border-top: 1px solid silver;
+ height: 1px;
+ text-align: left;
+ margin-left: 0;
+ width: 20%;
+ min-width: 100px;
+}
+
+div.colist td {
+ padding-right: 0.5em;
+ padding-bottom: 0.3em;
+ vertical-align: top;
+}
+div.colist td img {
+ margin-top: 0.3em;
+}
+
+@media print {
+ div#footer-badges { display: none; }
+}
+
+div#toc {
+ margin-bottom: 2.5em;
+}
+
+div#toctitle {
+ color: #527bbd;
+ font-family: sans-serif;
+ font-size: 1.1em;
+ font-weight: bold;
+ margin-top: 1.0em;
+ margin-bottom: 0.1em;
+}
+
+div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
+ margin-top: 0;
+ margin-bottom: 0;
+}
+div.toclevel2 {
+ margin-left: 2em;
+ font-size: 0.9em;
+}
+div.toclevel3 {
+ margin-left: 4em;
+ font-size: 0.9em;
+}
+div.toclevel4 {
+ margin-left: 6em;
+ font-size: 0.9em;
+}
+
+/* Overrides for manpage documents */
+h1 {
+ padding-top: 0.5em;
+ padding-bottom: 0.5em;
+ border-top: 2px solid silver;
+ border-bottom: 2px solid silver;
+}
+h2 {
+ border-style: none;
+}
+div.sectionbody {
+ margin-left: 5%;
+}
+
+@media print {
+ div#toc { display: none; }
+}
+
+</style>
+<script type="text/javascript">
+/*<+'])');
+ // Function that scans the DOM tree for header elements (the DOM2
+ // nodeIterator API would be a better technique but not supported by all
+ // browsers).
+ var iterate = function (el) {
+ for (var i = el.firstChild; i != null; i = i.nextSibling) {
+ if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
+ var mo = re.exec(i.tagName);
+ if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
+ result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
+ }
+ iterate(i);
+ }
+ }
+ }
+ iterate(el);
+ return result;
+ }
+
+ var toc = document.getElementById("toc");
+ var entries = tocEntries(document.getElementById("content"), toclevels);
+ for (var i = 0; i < entries.length; ++i) {
+ var entry = entries[i];
+ if (entry.element.id == "")
+ entry.element.id = "_toc_" + i;
+ var a = document.createElement("a");
+ a.href = "#" + entry.element.id;
+ a.appendChild(document.createTextNode(entry.text));
+ var div = document.createElement("div");
+ div.appendChild(a);
+ div.className = "toclevel" + entry.toclevel;
+ toc.appendChild(div);
+ }
+ if (entries.length == 0)
+ toc.parentNode.removeChild(toc);
+},
+
+
+/////////////////////////////////////////////////////////////////////
+// Footnotes generator
+/////////////////////////////////////////////////////////////////////
+
+/* Based on footnote generation code from:
+ * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
+ */
+
+footnotes: function () {
+ var cont = document.getElementById("content");
+ var noteholder = document.getElementById("footnotes");
+ var spans = cont.getElementsByTagName("span");
+ var refs = {};
+ var n = 0;
+ for (i=0; i<spans.length; i++) {
+ if (spans[i].className == "footnote") {
+ n++;
+ // Use [\s\S] in place of . so multi-line matches work.
+ // Because JavaScript has no s (dotall) regex flag.
+ note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
+ noteholder.innerHTML +=
+ "<div class='footnote' id='_footnote_" + n + "'>" +
+ "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
+ n + "</a>. " + note + "</div>";
+ spans[i].innerHTML =
+ "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
+ "' title='View footnote' class='footnote'>" + n + "</a>]";
+ var id =spans[i].getAttribute("id");
+ if (id != null) refs["#"+id] = n;
+ }
+ }
+ if (n == 0)
+ noteholder.parentNode.removeChild(noteholder);
+ else {
+ // Process footnoterefs.
+ for (i=0; i<spans.length; i++) {
+ if (spans[i].className == "footnoteref") {
+ var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
+ href = href.match(/#.*/)[0]; // Because IE return full URL.
+ n = refs[href];
+ spans[i].innerHTML =
+ "[<a href='#_footnote_" + n +
+ "' title='View footnote' class='footnote'>" + n + "</a>]";
+ }
+ }
+ }
+}
+
+}
+/*]]>*/
+</script>
+</head>
+<body class="manpage">
+<div id="header">
+<h1>
+Jim Tcl(n) Manual Page
+</h1>
+<h2>NAME</h2>
+<div class="sectionbody">
+<p>Jim Tcl v0.63 -
+ overview of the Jim tool command language facilities
+</p>
+</div>
+</div>
+<div id="content">
+<div class="sect1">
+<h2 id="_synopsis">SYNOPSIS</h2>
+<div class="sectionbody">
+<div class="literalblock">
+<div class="content">
+<pre><tt>cc <source> -ljim</tt></pre>
+</div></div>
+<div class="paragraph"><p>or</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>jimsh <script></tt></pre>
+</div></div>
+<div class="ulist"><div class="title">Quick Index</div><ul>
+<li>
+<p>
+<a href="#CommandIndex">Command Reference</a>
+</p>
+</li>
+<li>
+<p>
+<a href="#OperatorPrecedence">Operator Precedence</a>
+</p>
+</li>
+<li>
+<p>
+<a href="#BuiltinVariables">Builtin Variables</a>
+</p>
+</li>
+<li>
+<p>
+<a href="#BackslashSequences">Backslash Sequences</a>
+</p>
+</li>
+</ul></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_introduction">INTRODUCTION</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Jim is a reimplementation of Tcl, combining some features from
+earlier, smaller versions of Tcl (6.x) as well as more modern
+features from later versions of Tcl (7.x, 8.x). It also has some some
+entirely new features not available in any version of Tcl.</p></div>
+<div class="paragraph"><p>This version is approximately the same size as "tinytcl" (6.8) but
+is faster and has more features.</p></div>
+<div class="paragraph"><p>Note that most of this man page is the original 6.8 Tcl man page, with
+changes made for differences with Jim.</p></div>
+<div class="paragraph"><p>The major differences are:</p></div>
+<div class="olist arabic"><ol class="arabic">
+<li>
+<p>
+Object-based I/O (aio) with backward compatibility wrapper
+</p>
+</li>
+<li>
+<p>
+I/O: Support for sockets (client and server)
+</p>
+</li>
+<li>
+<p>
+I/O: Support for readable/writable event handlers
+</p>
+</li>
+<li>
+<p>
+Integers are 64bit
+</p>
+</li>
+<li>
+<p>
+Support for references (<em>ref</em>/<em>getref</em>/<em>setref</em>) and garbage collection
+</p>
+</li>
+<li>
+<p>
+Builtin dictionary type (<em>dict</em>)
+</p>
+</li>
+<li>
+<p>
+<em>file mkdir</em>, <em>file rename</em>, <em>file tempfile</em> (Tcl 7.x, 8.x)
+</p>
+</li>
+<li>
+<p>
+<em>env</em> command to access environment variables
+</p>
+</li>
+<li>
+<p>
+List: <em>lmap</em>, <em>lset</em>, <em>lreverse</em>, <em>lassign</em> (Tcl 8.x)
+</p>
+</li>
+<li>
+<p>
+<em>os.fork</em>, <em>os.wait</em>, <em>rand</em>
+</p>
+</li>
+<li>
+<p>
+<em>{*}</em>/<em>{expand}</em>
+</p>
+</li>
+<li>
+<p>
+<em>string map</em> (Tcl 7.x)
+</p>
+</li>
+<li>
+<p>
+<em>subst</em> (Tcl 7.x)
+</p>
+</li>
+<li>
+<p>
+<em>switch</em> (Tcl 7.x) (note that <em>case</em> is provided for compatibility)
+</p>
+</li>
+<li>
+<p>
+Much better error reporting. <em>info stacktrace</em> as a replacement for <em>errorInfo</em>, <em>errorCode</em>
+</p>
+</li>
+<li>
+<p>
+Support for "static" variables in procedures
+</p>
+</li>
+<li>
+<p>
+Significantly faster for many scripts/operations
+</p>
+</li>
+<li>
+<p>
+Support for tail-call optimisation, <em>tailcall</em>
+</p>
+</li>
+<li>
+<p>
+Variable traces are not supported
+</p>
+</li>
+<li>
+<p>
+The history command is not supported
+</p>
+</li>
+</ol></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_changes">CHANGES</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Since v0.62:</p></div>
+<div class="olist arabic"><ol class="arabic">
+<li>
+<p>
+<em>source</em> now checks that a script is complete (.i.e. not missing a brace)
+</p>
+</li>
+<li>
+<p>
+<em>info complete</em> now uses the real parser and so is 100% accurate
+</p>
+</li>
+<li>
+<p>
+Better access to live stack frames with <em>info frame</em>, <em>stacktrace</em> and <em>stackdump</em>
+</p>
+</li>
+<li>
+<p>
+<em>tailcall</em> no longer loses stack trace information
+</p>
+</li>
+<li>
+<p>
+Add <em>alias</em> and <em>curry</em>
+</p>
+</li>
+<li>
+<p>
+<em>lambda</em>, <em>alias</em> and <em>curry</em> are implemented via <em>tailcall</em> for efficiency
+</p>
+</li>
+<li>
+<p>
+<em>local</em> allows procedures to be deleted automatically at the end of the current procedure
+</p>
+</li>
+<li>
+<p>
+udp sockets are now supported for both clients and servers.
+</p>
+</li>
+<li>
+<p>
+vfork-based exec is now working correctly
+</p>
+</li>
+<li>
+<p>
+Add <em>file tempfile</em>
+</p>
+</li>
+<li>
+<p>
+Add <em>socket pipe</em>
+</p>
+</li>
+<li>
+<p>
+Enhance <em>try … on … finally</em> to be more Tcl 8.6 compatible
+</p>
+</li>
+<li>
+<p>
+It is now possible to <em>return</em> from within <em>try</em>
+</p>
+</li>
+<li>
+<p>
+IPv6 support is now included
+</p>
+</li>
+<li>
+<p>
+Add <em>string is</em>
+</p>
+</li>
+<li>
+<p>
+Event handlers works better if an error occurs. eof handler has been removed.
+</p>
+</li>
+<li>
+<p>
+<em>exec</em> now sets $::errorCode, and catch sets opts(-errorcode) for exit status
+</p>
+</li>
+<li>
+<p>
+Command pipelines via open "|…" are now supported
+</p>
+</li>
+<li>
+<p>
+<em>pid</em> can now return pids of a command pipeline
+</p>
+</li>
+<li>
+<p>
+Add <em>info references</em>
+</p>
+</li>
+<li>
+<p>
+Add support for <em>after <strong>ms</strong></em>, <em>after idle</em>, <em>after info</em>, <em>update</em>
+</p>
+</li>
+<li>
+<p>
+<em>exec</em> now sets environment based on $::env
+</p>
+</li>
+</ol></div>
+<div class="paragraph"><p>Since v0.61:</p></div>
+<div class="olist arabic"><ol class="arabic">
+<li>
+<p>
+Add support to <em>exec</em> for <em>>&</em>, <em>>>&</em>, <em>|&</em>, <em>2>@1</em>
+</p>
+</li>
+<li>
+<p>
+Fix <em>exec</em> error messages when special token (e.g. <em>></em>) is the last token
+</p>
+</li>
+<li>
+<p>
+Fix <em>subst</em> handling of backslash escapes.
+</p>
+</li>
+<li>
+<p>
+Allow abbreviated options for <em>subst</em>
+</p>
+</li>
+<li>
+<p>
+Add support for <em>return</em>, <em>break</em>, <em>continue</em> in subst
+</p>
+</li>
+<li>
+<p>
+Many <em>expr</em> bug fixes
+</p>
+</li>
+<li>
+<p>
+Add support for functions in <em>expr</em> (e.g. int(), abs()), and also <em>in</em>, <em>ni</em> list operations
+</p>
+</li>
+<li>
+<p>
+The variable name argument to <em>regsub</em> is now optional
+</p>
+</li>
+<li>
+<p>
+Add support for <em>unset -nocomplain</em>
+</p>
+</li>
+<li>
+<p>
+Add support for list commands: <em>lassign</em>, <em>lrepeat</em>
+</p>
+</li>
+<li>
+<p>
+Fully-functional <em>lsearch</em> is now implemented
+</p>
+</li>
+<li>
+<p>
+Add <em>info nameofexecutable</em> and <em>info returncodes</em>
+</p>
+</li>
+<li>
+<p>
+Allow <em>catch</em> to determine what return codes are caught
+</p>
+</li>
+<li>
+<p>
+Allow <em>incr</em> to increment an unset variable by first setting to 0
+</p>
+</li>
+<li>
+<p>
+Allow <em>args</em> and optional arguments to the left or required arguments in <em>proc</em>
+</p>
+</li>
+<li>
+<p>
+Add <em>file copy</em>
+</p>
+</li>
+<li>
+<p>
+Add <em>try … finally</em> command
+</p>
+</li>
+</ol></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_tcl_introduction">TCL INTRODUCTION</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Tcl stands for <em>tool command language</em> and is pronounced <em>tickle.</em>
+It is actually two things: a language and a library.</p></div>
+<div class="paragraph"><p>First, Tcl is a simple textual language, intended primarily for
+issuing commands to interactive programs such as text editors,
+debuggers, illustrators, and shells. It has a simple syntax and is also
+programmable, so Tcl users can write command procedures to provide more
+powerful commands than those in the built-in set.</p></div>
+<div class="paragraph"><p>Second, Tcl is a library package that can be embedded in application
+programs. The Tcl library consists of a parser for the Tcl language,
+routines to implement the Tcl built-in commands, and procedures that
+allow each application to extend Tcl with additional commands specific
+to that application. The application program generates Tcl commands and
+passes them to the Tcl parser for execution. Commands may be generated
+by reading characters from an input source, or by associating command
+strings with elements of the application’s user interface, such as menu
+entries, buttons, or keystrokes.</p></div>
+<div class="paragraph"><p>When the Tcl library receives commands it parses them into component
+fields and executes built-in commands directly. For commands implemented
+by the application, Tcl calls back to the application to execute the
+commands. In many cases commands will invoke recursive invocations of the
+Tcl interpreter by passing in additional strings to execute (procedures,
+looping commands, and conditional commands all work in this way).</p></div>
+<div class="paragraph"><p>An application program gains three advantages by using Tcl for its command
+language. First, Tcl provides a standard syntax: once users know Tcl,
+they will be able to issue commands easily to any Tcl-based application.
+Second, Tcl provides programmability. All a Tcl application needs
+to do is to implement a few application-specific low-level commands.
+Tcl provides many utility commands plus a general programming interface
+for building up complex command procedures. By using Tcl, applications
+need not re-implement these features.</p></div>
+<div class="paragraph"><p>Third, Tcl can be used as a common language for communicating between
+applications. Inter-application communication is not built into the
+Tcl core described here, but various add-on libraries, such as the Tk
+toolkit, allow applications to issue commands to each other. This makes
+it possible for applications to work together in much more powerful ways
+than was previously possible.</p></div>
+<div class="paragraph"><p>This manual page focuses primarily on the Tcl language. It describes
+the language syntax and the built-in commands that will be available
+in any application based on Tcl. The individual library procedures are
+described in more detail in separate manual pages, one per procedure.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_interpreters">INTERPRETERS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>The central data structure in Tcl is an interpreter (C type <em>Jim_Interp</em>).
+An interpreter consists of a set of command bindings, a set of variable
+values, and a few other miscellaneous pieces of state. Each Tcl command
+is interpreted in the context of a particular interpreter.</p></div>
+<div class="paragraph"><p>Some Tcl-based applications will maintain multiple interpreters
+simultaneously, each associated with a different widget or portion of
+the application. Interpreters are relatively lightweight structures.
+They can be created and deleted quickly, so application programmers should
+feel free to use multiple interpreters if that simplifies the application.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_data_types">DATA TYPES</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Tcl supports only one type of data: strings. All commands, all arguments
+to commands, all command results, and all variable values are strings.</p></div>
+<div class="paragraph"><p>Where commands require numeric arguments or return numeric results,
+the arguments and results are passed as strings. Many commands expect
+their string arguments to have certain formats, but this interpretation
+is up to the individual commands. For example, arguments often contain
+Tcl command strings, which may get executed as part of the commands.
+The easiest way to understand the Tcl interpreter is to remember that
+everything is just an operation on a string. In many cases Tcl constructs
+will look similar to more structured constructs from other languages.
+However, the Tcl constructs are not structured at all; they are just
+strings of characters, and this gives them a different behavior than
+the structures they may look like.</p></div>
+<div class="paragraph"><p>Although the exact interpretation of a Tcl string depends on who is doing
+the interpretation, there are three common forms that strings take:
+commands, expressions, and lists. The major sections below discuss
+these three forms in more detail.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_basic_command_syntax">BASIC COMMAND SYNTAX</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>The Tcl language has syntactic similarities to both the Unix shells
+and Lisp. However, the interpretation of commands is different
+in Tcl than in either of those other two systems.
+A Tcl command string consists of one or more commands separated
+by newline characters or semi-colons.
+Each command consists of a collection of fields separated by
+white space (spaces or tabs).
+The first field must be the name of a command, and the
+additional fields, if any, are arguments that will be passed to
+that command. For example, the command:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a 22</tt></pre>
+</div></div>
+<div class="paragraph"><p>has three fields: the first, <em>set</em>, is the name of a Tcl command, and
+the last two, <em>a</em> and <em>22</em>, will be passed as arguments to
+the <em>set</em> command. The command name may refer either to a built-in
+Tcl command, an application-specific command bound in with the library
+procedure <em>Jim_CreateCommand</em>, or a command procedure defined with the
+<em>proc</em> built-in command.</p></div>
+<div class="paragraph"><p>Arguments are passed literally as text strings. Individual commands may
+interpret those strings in any fashion they wish. The <em>set</em> command,
+for example, will treat its first argument as the name of a variable
+and its second argument as a string value to assign to that variable.
+For other commands arguments may be interpreted as integers, lists,
+file names, or Tcl commands.</p></div>
+<div class="paragraph"><p>Command names should normally be typed completely (e.g. no abbreviations).
+However, if the Tcl interpreter cannot locate a command it invokes a
+special command named <em>unknown</em> which attempts to find or create the
+command.</p></div>
+<div class="paragraph"><p>For example, at many sites <em>unknown</em> will search through library
+directories for the desired command and create it as a Tcl procedure if
+it is found. The <em>unknown</em> command often provides automatic completion
+of abbreviated commands, but usually only for commands that were typed
+interactively.</p></div>
+<div class="paragraph"><p>It’s probably a bad idea to use abbreviations in command scripts and
+other forms that will be re-used over time: changes to the command set
+may cause abbreviations to become ambiguous, resulting in scripts that
+no longer work.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_comments">COMMENTS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>If the first non-blank character in a command is <em>#</em>, then everything
+from the <em>\#</em> up through the next newline character is treated as
+a comment and ignored. When comments are embedded inside nested
+commands (e.g. fields enclosed in braces) they must have properly-matched
+braces (this is necessary because when Tcl parses the top-level command
+it doesn’t yet know that the nested field will be used as a command so
+it cannot process the nested comment character as a comment).</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_grouping_arguments_with_double_quotes">GROUPING ARGUMENTS WITH DOUBLE-QUOTES</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Normally each argument field ends at the next white space, but
+double-quotes may be used to create arguments with embedded space.</p></div>
+<div class="paragraph"><p>If an argument field begins with a double-quote, then the argument isn’t
+terminated by white space (including newlines) or a semi-colon (see below
+for information on semi-colons); instead it ends at the next double-quote
+character. The double-quotes are not included in the resulting argument.
+For example, the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a "This is a single argument"</tt></pre>
+</div></div>
+<div class="paragraph"><p>will pass two arguments to <em>set</em>: <em>a</em> and <em>This is a single argument</em>.</p></div>
+<div class="paragraph"><p>Within double-quotes, command substitutions, variable substitutions,
+and backslash substitutions still occur, as described below. If the
+first character of a command field is not a quote, then quotes receive
+no special interpretation in the parsing of that field.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_grouping_arguments_with_braces">GROUPING ARGUMENTS WITH BRACES</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Curly braces may also be used for grouping arguments. They are similar
+to quotes except for two differences. First, they nest; this makes them
+easier to use for complicated arguments like nested Tcl command strings.
+Second, the substitutions described below for commands, variables, and
+backslashes do <strong>not</strong> occur in arguments enclosed in braces, so braces
+can be used to prevent substitutions where they are undesirable.</p></div>
+<div class="paragraph"><p>If an argument field begins with a left brace, then the argument ends
+at the matching right brace. Tcl will strip off the outermost layer
+of braces and pass the information between the braces to the command
+without any further modification. For example, in the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a {xyz a {b c d}}</tt></pre>
+</div></div>
+<div class="paragraph"><p>the <em>set</em> command will receive two arguments: <em>a</em>
+and <em>xyz a {b c d}</em>.</p></div>
+<div class="paragraph"><p>When braces or quotes are in effect, the matching brace or quote need
+not be on the same line as the starting quote or brace; in this case
+the newline will be included in the argument field along with any other
+characters up to the matching brace or quote. For example, the <em>eval</em>
+command takes one argument, which is a command string; <em>eval</em> invokes
+the Tcl interpreter to execute the command string. The command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>eval {
+ set a 22
+ set b 33
+}</tt></pre>
+</div></div>
+<div class="paragraph"><p>will assign the value <em>22</em> to <em>a</em> and <em>33</em> to <em>b</em>.</p></div>
+<div class="paragraph"><p>If the first character of a command field is not a left
+brace, then neither left nor right
+braces in the field will be treated specially (except as part of
+variable substitution; see below).</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_command_substitution_with_brackets">COMMAND SUBSTITUTION WITH BRACKETS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>If an open bracket occurs in a field of a command, then command
+substitution occurs (except for fields enclosed in braces). All of the
+text up to the matching close bracket is treated as a Tcl command and
+executed immediately. Then the result of that command is substituted
+for the bracketed text. For example, consider the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a [set b]</tt></pre>
+</div></div>
+<div class="paragraph"><p>When the <em>set</em> command has only a single argument, it is the name of a
+variable and <em>set</em> returns the contents of that variable. In this case,
+if variable <em>b</em> has the value <em>foo</em>, then the command above is equivalent
+to the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a foo</tt></pre>
+</div></div>
+<div class="paragraph"><p>Brackets can be used in more complex ways. For example, if the variable
+<em>b</em> has the value <em>foo</em> and the variable <em>c</em> has the value <em>gorp</em>,
+then the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a xyz[set b].[set c]</tt></pre>
+</div></div>
+<div class="paragraph"><p>is equivalent to the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a xyzfoo.gorp</tt></pre>
+</div></div>
+<div class="paragraph"><p>A bracketed command may contain multiple commands separated by newlines
+or semi-colons in the usual fashion. In this case the value of the last
+command is used for substitution. For example, the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a x[set b 22
+expr $b+2]x</tt></pre>
+</div></div>
+<div class="paragraph"><p>is equivalent to the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a x24x</tt></pre>
+</div></div>
+<div class="paragraph"><p>If a field is enclosed in braces then the brackets and the characters
+between them are not interpreted specially; they are passed through to
+the argument verbatim.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_variable_substitution_with">VARIABLE SUBSTITUTION WITH $</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>The dollar sign (<em>$</em>) may be used as a special shorthand form for
+substituting variable values. If <em>$</em> appears in an argument that isn’t
+enclosed in braces then variable substitution will occur. The characters
+after the <em>$</em>, up to the first character that isn’t a number, letter,
+or underscore, are taken as a variable name and the string value of that
+variable is substituted for the name.</p></div>
+<div class="paragraph"><p>For example, if variable <em>foo</em> has the value <em>test</em>, then the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a $foo.c</tt></pre>
+</div></div>
+<div class="paragraph"><p>is equivalent to the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a test.c</tt></pre>
+</div></div>
+<div class="paragraph"><p>There are two special forms for variable substitution. If the next
+character after the name of the variable is an open parenthesis, then
+the variable is assumed to be an array name, and all of the characters
+between the open parenthesis and the next close parenthesis are taken as
+an index into the array. Command substitutions and variable substitutions
+are performed on the information between the parentheses before it is
+used as an index.</p></div>
+<div class="paragraph"><p>For example, if the variable <em>x</em> is an array with one element named
+<em>first</em> and value <em>87</em> and another element named <em>14</em> and value <em>more</em>,
+then the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a xyz$x(first)zyx</tt></pre>
+</div></div>
+<div class="paragraph"><p>is equivalent to the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a xyz87zyx</tt></pre>
+</div></div>
+<div class="paragraph"><p>If the variable <em>index</em> has the value <em>14</em>, then the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a xyz$x($index)zyx</tt></pre>
+</div></div>
+<div class="paragraph"><p>is equivalent to the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a xyzmorezyx</tt></pre>
+</div></div>
+<div class="paragraph"><p>For more information on arrays, see VARIABLES AND ARRAYS below.</p></div>
+<div class="paragraph"><p>The second special form for variables occurs when the dollar sign is
+followed by an open curly brace. In this case the variable name consists
+of all the characters up to the next curly brace.</p></div>
+<div class="paragraph"><p>Array references are not possible in this form: the name between braces
+is assumed to refer to a scalar variable. For example, if variable
+<em>foo</em> has the value <em>test</em>, then the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a abc${foo}bar</tt></pre>
+</div></div>
+<div class="paragraph"><p>is equivalent to the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a abctestbar</tt></pre>
+</div></div>
+<div class="paragraph"><p>Variable substitution does not occur in arguments that are enclosed in
+braces: the dollar sign and variable name are passed through to the
+argument verbatim.</p></div>
+<div class="paragraph"><p>The dollar sign abbreviation is simply a shorthand form. <em>$a</em> is
+completely equivalent to <em>[set a]</em>; it is provided as a convenience
+to reduce typing.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_separating_commands_with_semi_colons">SEPARATING COMMANDS WITH SEMI-COLONS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Normally, each command occupies one line (the command is terminated by a
+newline character). However, semi-colon (<em>;</em>) is treated as a command
+separator character; multiple commands may be placed on one line by
+separating them with a semi-colon. Semi-colons are not treated as
+command separators if they appear within curly braces or double-quotes.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_backslash_substitution">BACKSLASH SUBSTITUTION</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Backslashes may be used to insert non-printing characters into command
+fields and also to insert special characters like braces and brackets
+into fields without them being interpreted specially as described above.</p></div>
+<div class="paragraph"><p>The backslash sequences understood by the Tcl interpreter are
+listed below. In each case, the backslash
+sequence is replaced by the given character:</p></div>
+<div class="dlist" id="BackslashSequences"><dl>
+<dt class="hdlist1">
+<tt>\b</tt>
+</dt>
+<dd>
+<p>
+ Backspace (0x8)
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>\f</tt>
+</dt>
+<dd>
+<p>
+ Form feed (0xc)
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>\n</tt>
+</dt>
+<dd>
+<p>
+ Newline (0xa)
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>\r</tt>
+</dt>
+<dd>
+<p>
+ Carriage-return (0xd).
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>\t</tt>
+</dt>
+<dd>
+<p>
+ Tab (0x9).
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>\v</tt>
+</dt>
+<dd>
+<p>
+ Vertical tab (0xb).
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>\{</tt>
+</dt>
+<dd>
+<p>
+ Left brace ({).
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>\}</tt>
+</dt>
+<dd>
+<p>
+ Right brace (}).
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>\[</tt>
+</dt>
+<dd>
+<p>
+ Open bracket ([).
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>\]</tt>
+</dt>
+<dd>
+<p>
+ Close bracket (]).
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>\$</tt>
+</dt>
+<dd>
+<p>
+ Dollar sign ($).
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>\<space></tt>
+</dt>
+<dd>
+<p>
+ Space ( ): doesn’t terminate argument.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>\;</tt>
+</dt>
+<dd>
+<p>
+ Semi-colon: doesn’t terminate command.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>\"</tt>
+</dt>
+<dd>
+<p>
+ Double-quote.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>\<newline></tt>
+</dt>
+<dd>
+<p>
+ Nothing: this joins two lines together
+ into a single line. This backslash feature is unique in that
+ it will be applied even when the sequence occurs within braces.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>\\</tt>
+</dt>
+<dd>
+<p>
+ Backslash (<em>\</em>).
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>\<strong>ddd</strong></tt>
+</dt>
+<dd>
+<p>
+ The digits <strong>ddd</strong> (one, two, or three of them) give the octal value of
+ the character. Note that Jim supports null characters in strings.
+</p>
+</dd>
+</dl></div>
+<div class="paragraph"><p>For example, in the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a \{x\[\ yz\141</tt></pre>
+</div></div>
+<div class="paragraph"><p>the second argument to <em>set</em> will be <em>{x[ yza</em>.</p></div>
+<div class="paragraph"><p>If a backslash is followed by something other than one of the options
+described above, then the backslash is transmitted to the argument
+field without any special processing, and the Tcl scanner continues
+normal processing with the next character. For example, in the
+command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set \*a \\\{foo</tt></pre>
+</div></div>
+<div class="paragraph"><p>The first argument to <em>set</em> will be <em>\*a</em> and the second
+argument will be <em>\{foo</em>.</p></div>
+<div class="paragraph"><p>If an argument is enclosed in braces, then backslash sequences inside
+the argument are parsed but no substitution occurs (except for
+backslash-newline): the backslash
+sequence is passed through to the argument as is, without making
+any special interpretation of the characters in the backslash sequence.
+In particular, backslashed braces are not counted in locating the
+matching right brace that terminates the argument.
+For example, in the
+command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a {\{abc}</tt></pre>
+</div></div>
+<div class="paragraph"><p>the second argument to <em>set</em> will be <em>\{abc</em>.</p></div>
+<div class="paragraph"><p>This backslash mechanism is not sufficient to generate absolutely
+any argument structure; it only covers the
+most common cases. To produce particularly complicated arguments
+it is probably easiest to use the <em>format</em> command along with
+command substitution.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_string_and_list_index_specifications">STRING AND LIST INDEX SPECIFICATIONS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Many string and list commands take one or more <em>index</em> parameters which
+specify a position in the string relative to the start or end of the string/list.</p></div>
+<div class="paragraph"><p>The index may be one of the following forms:</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt>integer</tt>
+</dt>
+<dd>
+<p>
+ A simple integer, where <em>0</em> refers to the first element of the string
+ or list.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>integer+integer</tt> or
+</dt>
+<dt class="hdlist1">
+<tt>integer-integer</tt>
+</dt>
+<dd>
+<p>
+ The sum or difference of the two integers. e.g. <tt>2+3</tt> refers to the 5th element.
+ This is useful when used with (e.g.) <tt>$i+1</tt> rather than the more verbose
+ <tt>[expr {$i+1}]</tt>
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>end</tt>
+</dt>
+<dd>
+<p>
+ The last element of the string or list.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>end-integer</tt>
+</dt>
+<dd>
+<p>
+ The <em>nth-from-last</em> element of the string or list.
+</p>
+</dd>
+</dl></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_command_summary">COMMAND SUMMARY</h2>
+<div class="sectionbody">
+<div class="olist arabic"><ol class="arabic">
+<li>
+<p>
+A command is just a string.
+</p>
+</li>
+<li>
+<p>
+Within a string commands are separated by newlines or semi-colons
+ (unless the newline or semi-colon is within braces or brackets
+ or is backslashed).
+</p>
+</li>
+<li>
+<p>
+A command consists of fields. The first field is the name of the command.
+ The other fields are strings that are passed to that command as arguments.
+</p>
+</li>
+<li>
+<p>
+Fields are normally separated by white space.
+</p>
+</li>
+<li>
+<p>
+Double-quotes allow white space and semi-colons to appear within
+ a single argument.
+ Command substitution, variable substitution, and backslash substitution
+ still occur inside quotes.
+</p>
+</li>
+<li>
+<p>
+Braces defer interpretation of special characters.
+ If a field begins with a left brace, then it consists of everything
+ between the left brace and the matching right brace. The
+ braces themselves are not included in the argument.
+ No further processing is done on the information between the braces
+ except that backslash-newline sequences are eliminated.
+</p>
+</li>
+<li>
+<p>
+If a field doesn’t begin with a brace then backslash,
+ variable, and command substitution are done on the field. Only a
+ single level of processing is done: the results of one substitution
+ are not scanned again for further substitutions or any other
+ special treatment. Substitution can
+ occur on any field of a command, including the command name
+ as well as the arguments.
+</p>
+</li>
+<li>
+<p>
+If the first non-blank character of a command is a <em>#</em>, everything
+ from the <em>\#</em> up through the next newline is treated as a comment
+ and ignored.
+</p>
+</li>
+</ol></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_expressions">EXPRESSIONS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>The second major interpretation applied to strings in Tcl is
+as expressions. Several commands, such as <em>expr</em>, <em>for</em>,
+and <em>if</em>, treat one or more of their arguments as expressions
+and call the Tcl expression processors (<em>Jim_ExprLong</em>,
+<em>Jim_ExprBoolean</em>, etc.) to evaluate them.</p></div>
+<div class="paragraph"><p>The operators permitted in Tcl expressions are a subset of
+the operators permitted in C expressions, and they have the
+same meaning and precedence as the corresponding C operators.
+Expressions almost always yield numeric results
+(integer or floating-point values).
+For example, the expression</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>8.2 + 6</tt></pre>
+</div></div>
+<div class="paragraph"><p>evaluates to 14.2.</p></div>
+<div class="paragraph"><p>Tcl expressions differ from C expressions in the way that
+operands are specified, and in that Tcl expressions support
+non-numeric operands and string comparisons.</p></div>
+<div class="paragraph"><p>A Tcl expression consists of a combination of operands, operators,
+and parentheses.</p></div>
+<div class="paragraph"><p>White space may be used between the operands and operators and
+parentheses; it is ignored by the expression processor.
+Where possible, operands are interpreted as integer values.</p></div>
+<div class="paragraph"><p>Integer values may be specified in decimal (the normal case), in octal (if the
+first character of the operand is <em>0</em>), or in hexadecimal (if the first
+two characters of the operand are <em>0x</em>).</p></div>
+<div class="paragraph"><p>If an operand does not have one of the integer formats given
+above, then it is treated as a floating-point number if that is
+possible. Floating-point numbers may be specified in any of the
+ways accepted by an ANSI-compliant C compiler (except that the
+<em>f</em>, <em>F</em>, <em>l</em>, and <em>L</em> suffixes will not be permitted in
+most installations). For example, all of the
+following are valid floating-point numbers: 2.1, 3., 6e4, 7.91e+16.</p></div>
+<div class="paragraph"><p>If no numeric interpretation is possible, then an operand is left
+as a string (and only a limited set of operators may be applied to
+it).</p></div>
+<div class="olist arabic"><ol class="arabic">
+<li>
+<p>
+Operands may be specified in any of the following ways:
+</p>
+</li>
+<li>
+<p>
+As a numeric value, either integer or floating-point.
+</p>
+</li>
+<li>
+<p>
+As a Tcl variable, using standard <em>$</em> notation.
+The variable’s value will be used as the operand.
+</p>
+</li>
+<li>
+<p>
+As a string enclosed in double-quotes.
+The expression parser will perform backslash, variable, and
+command substitutions on the information between the quotes,
+and use the resulting value as the operand
+</p>
+</li>
+<li>
+<p>
+As a string enclosed in braces.
+The characters between the open brace and matching close brace
+will be used as the operand without any substitutions.
+</p>
+</li>
+<li>
+<p>
+As a Tcl command enclosed in brackets.
+The command will be executed and its result will be used as
+the operand.
+</p>
+</li>
+</ol></div>
+<div class="paragraph"><p>Where substitutions occur above (e.g. inside quoted strings), they
+are performed by the expression processor.
+However, an additional layer of substitution may already have
+been performed by the command parser before the expression
+processor was called.</p></div>
+<div class="paragraph"><p>As discussed below, it is usually best to enclose expressions
+in braces to prevent the command parser from performing substitutions
+on the contents.</p></div>
+<div class="paragraph"><p>For some examples of simple expressions, suppose the variable <em>a</em> has
+the value 3 and the variable <em>b</em> has the value 6. Then the expression
+on the left side of each of the lines below will evaluate to the value
+on the right side of the line:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>$a + 3.1 6.1
+2 + "$a.$b" 5.6
+4*[llength "6 2"] 8
+{word one} < "word $a" 0</tt></pre>
+</div></div>
+<div class="paragraph"><p>The valid operators are listed below, grouped in decreasing order
+of precedence:</p></div>
+<div class="dlist" id="OperatorPrecedence"><dl>
+<dt class="hdlist1">
+<tt>int() double() round() abs()</tt>
+</dt>
+<dd>
+<p>
+ Unary functions.
+ int() converts the numeric argument to an integer by truncating down.
+ double() converts the numeric argument to floating point.
+ round() converts the numeric argument to the closest integer value.
+ abs() takes the absolute value of the numeric argument.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>sin() cos() tan() asin() acos() atan() sinh() cosh() tanh() ceil() floor() exp() log() log10() sqrt()</tt>
+</dt>
+<dd>
+<p>
+ Unary math functions.
+ If Jim is compiled with math support, these functions are available.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>- + ~ !</tt>
+</dt>
+<dd>
+<p>
+ Unary minus, unary plus, bit-wise NOT, logical NOT. None of these operands
+ may be applied to string operands, and bit-wise NOT may be
+ applied only to integers.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>**</tt>
+</dt>
+<dd>
+<p>
+ Power. e.g. pow(). If Jim is compiled with math support, supports doubles and
+ integers. Otherwise supports integers only.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>* / %</tt>
+</dt>
+<dd>
+<p>
+ Multiply, divide, remainder. None of these operands may be
+ applied to string operands, and remainder may be applied only
+ to integers.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>+ -</tt>
+</dt>
+<dd>
+<p>
+ Add and subtract. Valid for any numeric operands.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><< >> <<< >>></tt>
+</dt>
+<dd>
+<p>
+ Left and right shift, left and right rotate. Valid for integer operands only.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>< > \<= >=</tt>
+</dt>
+<dd>
+<p>
+ Boolean less, greater, less than or equal, and greater than or equal.
+ Each operator produces 1 if the condition is true, 0 otherwise.
+ These operators may be applied to strings as well as numeric operands,
+ in which case string comparison is used.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>== !=</tt>
+</dt>
+<dd>
+<p>
+ Boolean equal and not equal. Each operator produces a zero/one result.
+ Valid for all operand types. <strong>Note</strong> that values will be converted to integers
+ if possible, then floating point types, and finally strings will be compared.
+ It is recommended that <em>eq</em> and <em>ne</em> should be used for string comparison.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>eq ne</tt>
+</dt>
+<dd>
+<p>
+ String equal and not equal. Uses the string value directly without
+ attempting to convert to a number first.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>in ni</tt>
+</dt>
+<dd>
+<p>
+ String in list and not in list. For <em>in</em>, result is 1 if the left operand (as a string)
+ is contained in the right operand (as a list), or 0 otherwise. The result for
+ <em>{$a ni $list}</em> is equivalent to <em>{!($a in $list)}</em>.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>&</tt>
+</dt>
+<dd>
+<p>
+ Bit-wise AND. Valid for integer operands only.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>|</tt>
+</dt>
+<dd>
+<p>
+ Bit-wise OR. Valid for integer operands only.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>^</tt>
+</dt>
+<dd>
+<p>
+ Bit-wise exclusive OR. Valid for integer operands only.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>&&</tt>
+</dt>
+<dd>
+<p>
+ Logical AND. Produces a 1 result if both operands are non-zero, 0 otherwise.
+ Valid for numeric operands only (integers or floating-point).
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>||</tt>
+</dt>
+<dd>
+<p>
+ Logical OR. Produces a 0 result if both operands are zero, 1 otherwise.
+ Valid for numeric operands only (integers or floating-point).
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>x ? y : z</tt>
+</dt>
+<dd>
+<p>
+ If-then-else, as in C. If <strong>x</strong>
+ evaluates to non-zero, then the result is the value of <strong>y</strong>.
+ Otherwise the result is the value of <strong>z</strong>.
+ The <strong>x</strong> operand must have a numeric value, while <strong>y</strong> and <strong>z</strong> can
+ be of any type.
+</p>
+</dd>
+</dl></div>
+<div class="paragraph"><p>See the C manual for more details on the results
+produced by each operator.
+All of the binary operators group left-to-right within the same
+precedence level. For example, the expression</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>4*2 < 7</tt></pre>
+</div></div>
+<div class="paragraph"><p>evaluates to 0.</p></div>
+<div class="paragraph"><p>The <em>&&</em>, <em>||</em>, and <em>?:</em> operators have <em>lazy
+evaluation</em>, just as in C,
+which means that operands are not evaluated if they are
+not needed to determine the outcome. For example, in</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>$v ? [a] : [b]</tt></pre>
+</div></div>
+<div class="paragraph"><p>only one of <em>[a]</em> or <em>[b]</em> will actually be evaluated,
+depending on the value of <em>$v</em>.</p></div>
+<div class="paragraph"><p>All internal computations involving integers are done with the C
+type <em>long long</em> if available, or <em>long</em> otherwise, and all internal
+computations involving floating-point are done with the C type
+<em>double</em>.</p></div>
+<div class="paragraph"><p>When converting a string to floating-point, exponent overflow is
+detected and results in a Tcl error.
+For conversion to integer from string, detection of overflow depends
+on the behavior of some routines in the local C library, so it should
+be regarded as unreliable.
+In any case, overflow and underflow are generally not detected
+reliably for intermediate results.</p></div>
+<div class="paragraph"><p>Conversion among internal representations for integer, floating-point,
+and string operands is done automatically as needed.
+For arithmetic computations, integers are used until some
+floating-point number is introduced, after which floating-point is used.
+For example,</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>5 / 4</tt></pre>
+</div></div>
+<div class="paragraph"><p>yields the result 1, while</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>5 / 4.0
+5 / ( [string length "abcd"] + 0.0 )</tt></pre>
+</div></div>
+<div class="paragraph"><p>both yield the result 1.25.</p></div>
+<div class="paragraph"><p>String values may be used as operands of the comparison operators,
+although the expression evaluator tries to do comparisons as integer
+or floating-point when it can.
+If one of the operands of a comparison is a string and the other
+has a numeric value, the numeric operand is converted back to
+a string using the C <em>sprintf</em> format specifier
+<em>%d</em> for integers and <em>%g</em> for floating-point values.
+For example, the expressions</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>"0x03" > "2"
+"0y" < "0x12"</tt></pre>
+</div></div>
+<div class="paragraph"><p>both evaluate to 1. The first comparison is done using integer
+comparison, and the second is done using string comparison after
+the second operand is converted to the string <em>18</em>.</p></div>
+<div class="paragraph"><p>In general it is safest to enclose an expression in braces when
+entering it in a command: otherwise, if the expression contains
+any white space then the Tcl interpreter will split it
+among several arguments. For example, the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>expr $a + $b</tt></pre>
+</div></div>
+<div class="paragraph"><p>results in three arguments being passed to <em>expr</em>: <em>$a</em>,
+<em>+</em>, and <em>$b</em>. In addition, if the expression isn’t in braces
+then the Tcl interpreter will perform variable and command substitution
+immediately (it will happen in the command parser rather than in
+the expression parser). In many cases the expression is being
+passed to a command that will evaluate the expression later (or
+even many times if, for example, the expression is to be used to
+decide when to exit a loop). Usually the desired goal is to re-do
+the variable or command substitutions each time the expression is
+evaluated, rather than once and for all at the beginning. For example,
+the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>for {set i 1} $i<=10 {incr i} {...} *** WRONG ***</tt></pre>
+</div></div>
+<div class="paragraph"><p>is probably intended to iterate over all values of <tt>i</tt> from 1 to 10.
+After each iteration of the body of the loop, <em>for</em> will pass
+its second argument to the expression evaluator to see whether or not
+to continue processing. Unfortunately, in this case the value of <tt>i</tt>
+in the second argument will be substituted once and for all when the
+<em>for</em> command is parsed. If <tt>i</tt> was 0 before the <em>for</em>
+command was invoked then for’s second argument will be <tt>0\<=10</tt>
+which will always evaluate to 1, even though <tt>i</tt> eventually
+becomes greater than 10. In the above case the loop will never
+terminate. Instead, the expression should be placed in braces:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>for {set i 1} {$i<=10} {incr i} {...} *** RIGHT ***</tt></pre>
+</div></div>
+<div class="paragraph"><p>This causes the substitution of <em>i</em>
+to be delayed; it will be re-done each time the expression is
+evaluated, which is the desired result.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_lists">LISTS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>The third major way that strings are interpreted in Tcl is as lists.
+A list is just a string with a list-like structure
+consisting of fields separated by white space. For example, the
+string</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>Al Sue Anne John</tt></pre>
+</div></div>
+<div class="paragraph"><p>is a list with four elements or fields.
+Lists have the same basic structure as command strings, except
+that a newline character in a list is treated as a field separator
+just like space or tab. Conventions for braces and quotes
+and backslashes are the same for lists as for commands. For example,
+the string</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>a b\ c {d e {f g h}}</tt></pre>
+</div></div>
+<div class="paragraph"><p>is a list with three elements: <em>a</em>, <em>b c</em>, and <em>d e {f g h}</em>.</p></div>
+<div class="paragraph"><p>Whenever an element is extracted from a list, the same rules about
+braces and quotes and backslashes are applied as for commands. Thus in
+the example above when the third element is extracted from the list,
+the result is</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>d e {f g h}</tt></pre>
+</div></div>
+<div class="paragraph"><p>(when the field was extracted, all that happened was to strip off
+the outermost layer of braces). Command substitution and
+variable substitution are never
+made on a list (at least, not by the list-processing commands; the
+list can always be passed to the Tcl interpreter for evaluation).</p></div>
+<div class="paragraph"><p>The Tcl commands <em>concat</em>, <em>foreach</em>, <em>lappend</em>, <em>lindex</em>, <em>linsert</em>,
+<em>list</em>, <em>llength</em>, <em>lrange</em>, <em>lreplace</em>, <em>lsearch</em>, and <em>lsort</em> allow
+you to build lists, extract elements from them, search them, and perform
+other list-related functions.</p></div>
+<div class="paragraph"><p>Advanced list commands include <em>lrepeat</em>, <em>lreverse</em>, <em>lmap</em>, <em>lassign</em>, <em>lset</em>.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_list_expansion">LIST EXPANSION</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>A new addition to Tcl 8.5 is the ability to expand a list into separate
+arguments. Support for this feature is also available in Jim.</p></div>
+<div class="paragraph"><p>Consider the following attempt to exec a list:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set cmd {ls -l}
+exec $cmd</tt></pre>
+</div></div>
+<div class="paragraph"><p>This will attempt to exec the a command named "ls -l", which will clearly not
+work. Typically eval and concat are required to solve this problem, however
+it can be solved much more easily with <em>{*}</em>.</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>exec {*}$cmd</tt></pre>
+</div></div>
+<div class="paragraph"><p>This will expand the following argument into individual elements and then evaluate
+the resulting command.</p></div>
+<div class="paragraph"><p>Note that the official Tcl syntax is <em>{*}</em>, however <em>{expand}</em> is retained
+for backward compatibility with experimental versions of this feature.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_regular_expressions">REGULAR EXPRESSIONS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Tcl provides two commands that support string matching using
+<em>egrep</em>-style regular expressions: <em>regexp</em> and <em>regsub</em>.</p></div>
+<div class="paragraph"><p>Regular expressions are implemented using the system’s C library as
+Extended Regular Expressions (EREs) rather than Basic Regular Expressions (BREs).</p></div>
+<div class="paragraph"><p>See regex(3) and regex(7) for full details.</p></div>
+<div class="paragraph"><p><strong>NOTE</strong> Tcl 7.x and 8.x use perl-style Advanced Regular Expressions (AREs).</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_command_results">COMMAND RESULTS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Each command produces two results: a code and a string. The
+code indicates whether the command completed successfully or not,
+and the string gives additional information. The valid codes are
+defined in jim.h, and are:</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt>JIM_OK(0)</tt>
+</dt>
+<dd>
+<p>
+ This is the normal return code, and indicates that the command completed
+ successfully. The string gives the command’s return value.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>JIM_ERR(1)</tt>
+</dt>
+<dd>
+<p>
+ Indicates that an error occurred; the string gives a message describing
+ the error.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>JIM_RETURN(2)</tt>
+</dt>
+<dd>
+<p>
+ Indicates that the <em>return</em> command has been invoked, and that the
+ current procedure (or top-level command or <em>source</em> command)
+ should return immediately. The
+ string gives the return value for the procedure or command.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>JIM_BREAK(3)</tt>
+</dt>
+<dd>
+<p>
+ Indicates that the <em>break</em> command has been invoked, so the
+ innermost loop should abort immediately. The string should always
+ be empty.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>JIM_CONTINUE(4)</tt>
+</dt>
+<dd>
+<p>
+ Indicates that the <em>continue</em> command has been invoked, so the
+ innermost loop should go on to the next iteration. The string
+ should always be empty.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>JIM_SIGNAL(5)</tt>
+</dt>
+<dd>
+<p>
+ Indicates that a signal was caught while executing a commands.
+ The string contains the name of the signal caught.
+ See the <em>signal</em> and <em>catch</em> commands.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>JIM_EXIT(6)</tt>
+</dt>
+<dd>
+<p>
+ Indicates that the command called the <em>exit</em> command.
+ The string contains the exit code.
+</p>
+</dd>
+</dl></div>
+<div class="paragraph"><p>Tcl programmers do not normally need to think about return codes,
+since <tt>JIM_OK</tt> is almost always returned. If anything else is returned
+by a command, then the Tcl interpreter immediately stops processing
+commands and returns to its caller. If there are several nested
+invocations of the Tcl interpreter in progress, then each nested
+command will usually return the error to its caller, until eventually
+the error is reported to the top-level application code. The
+application will then display the error message for the user.</p></div>
+<div class="paragraph"><p>In a few cases, some commands will handle certain <em>error</em> conditions
+themselves and not return them upwards. For example, the <em>for</em>
+command checks for the <tt>JIM_BREAK</tt> code; if it occurs, then <em>for</em>
+stops executing the body of the loop and returns <tt>JIM_OK</tt> to its
+caller. The <em>for</em> command also handles <tt>JIM_CONTINUE</tt> codes and the
+procedure interpreter handles <tt>JIM_RETURN</tt> codes. The <em>catch</em>
+command allows Tcl programs to catch errors and handle them without
+aborting command interpretation any further.</p></div>
+<div class="paragraph"><p>The <em>info returncodes</em> command may be used to programmatically map between
+return codes and names.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_procedures">PROCEDURES</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Tcl allows you to extend the command interface by defining
+procedures. A Tcl procedure can be invoked just like any other Tcl
+command (it has a name and it receives one or more arguments).
+The only difference is that its body isn’t a piece of C code linked
+into the program; it is a string containing one or more other
+Tcl commands.</p></div>
+<div class="paragraph"><p>The <em>proc</em> command is used to create a new Tcl command procedure:</p></div>
+<div class="paragraph"><p><tt><strong>proc</strong> <em>name args ?statics? body</em></tt></p></div>
+<div class="paragraph"><p>The new command is name <strong>name</strong>, and it replaces any existing command
+there may have been by that name. Whenever the new command is
+invoked, the contents of <strong>body</strong> will be executed by the Tcl
+interpreter.</p></div>
+<div class="paragraph"><p><strong>args</strong> specifies the formal arguments to the procedure.
+It consists of a list, possibly empty, of the following
+argument specifiers:</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt>name</tt>
+</dt>
+<dd>
+<p>
+ Required Argument - A simple argument name.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>name default</tt>
+</dt>
+<dd>
+<p>
+ Optional Argument - A two-element list consisting of the
+ argument name, followed by the default value, which will
+ be used if the corresponding argument is not supplied.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>args</strong></tt>
+</dt>
+<dd>
+<p>
+ Variable Argument - The special name <em>args</em>, which is
+ assigned all remaining arguments (including none). The
+ variable argument may only be specified once.
+</p>
+</dd>
+</dl></div>
+<div class="paragraph"><p>Arguments must be provided in the following order, any of which
+may be omitted:</p></div>
+<div class="olist arabic"><ol class="arabic">
+<li>
+<p>
+Required Arguments (Left)
+</p>
+</li>
+<li>
+<p>
+Optional Arguments
+</p>
+</li>
+<li>
+<p>
+Variable Argument
+</p>
+</li>
+<li>
+<p>
+Required Arguments (Right)
+</p>
+</li>
+</ol></div>
+<div class="paragraph"><p>When the command is invoked, a local variable will be created for each of
+the formal arguments to the procedure; its value will be the value
+of corresponding argument in the invoking command or the argument’s
+default value.</p></div>
+<div class="paragraph"><p>Arguments with default values need not be specified in a procedure
+invocation. However, there must be enough actual arguments for all
+required arguments, and there must not be any extra actual arguments
+(unless the Variable Argument is specified).</p></div>
+<div class="paragraph"><p>Actual arguments are assigned to formal arguments as follows:</p></div>
+<div class="olist arabic"><ol class="arabic">
+<li>
+<p>
+Left Required Arguments are assigned from the left
+</p>
+</li>
+<li>
+<p>
+Right Required Arguments are assigned from the right
+</p>
+</li>
+<li>
+<p>
+Default Arguments are assigned from the left, following the Left Required Arguments.
+</p>
+</li>
+<li>
+<p>
+A list is formed from any remaining arguments, which are then
+ are assigned to the <em>args</em> Variable Argument (if specified). The list will be empty
+ if there are no remaining arguments.
+</p>
+</li>
+</ol></div>
+<div class="paragraph"><p>When <strong>body</strong> is being executed, variable names normally refer to local
+variables, which are created automatically when referenced and deleted
+when the procedure returns. One local variable is automatically created
+for each of the procedure’s arguments. Global variables can be
+accessed by invoking the <em>global</em> command or via the <em>::</em> prefix.</p></div>
+<div class="paragraph"><p><strong>New in Jim</strong></p></div>
+<div class="paragraph"><p>In addition to procedure arguments, Jim procedures may declare static variables.
+These variables scoped to the procedure and initialised at procedure definition.
+Either from the static variable definition, or from the enclosing scope.</p></div>
+<div class="paragraph"><p>Consider the following example:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>jim> set a 1
+jim> proc a {} {a {b 2}} {
+ set c 1
+ puts "$a $b $c"
+ incr a
+ incr b
+ incr c
+}
+jim> a
+1 2 1
+jim> a
+2 3 1</tt></pre>
+</div></div>
+<div class="paragraph"><p>The static variable <strong>a</strong> has no initialiser, so it is initialised from
+the enclosing scope with the value 1. (Note that it is an error if there
+is no variable with the same name in the enclosing scope). However <strong>b</strong>
+has an initialiser, so it is initialised to 2.</p></div>
+<div class="paragraph"><p>Unlike a local variable, the value of a static variable is retained across
+invocations of the procedure.</p></div>
+<div class="paragraph"><p>See the <em>proc</em> command for information on
+how to define procedures and what happens when they are invoked.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_variables_scalars_and_arrays">VARIABLES - SCALARS AND ARRAYS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Tcl allows the definition of variables and the use of their values
+either through <em>$</em>-style variable substitution, the <em>set</em>
+command, or a few other mechanisms.</p></div>
+<div class="paragraph"><p>Variables need not be declared: a new variable will automatically
+be created each time a new variable name is used.</p></div>
+<div class="paragraph"><p>Tcl supports two types of variables: scalars and arrays.
+A scalar variable has a single value, whereas an array variable
+can have any number of elements, each with a name (called
+its <em>index</em>) and a value.</p></div>
+<div class="paragraph"><p>Array indexes may be arbitrary strings; they need not be numeric.
+Parentheses are used refer to array elements in Tcl commands.
+For example, the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set x(first) 44</tt></pre>
+</div></div>
+<div class="paragraph"><p>will modify the element of <em>x</em> whose index is <em>first</em>
+so that its new value is <em>44</em>.</p></div>
+<div class="paragraph"><p>Two-dimensional arrays can be simulated in Tcl by using indexes
+that contain multiple concatenated values.
+For example, the commands</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a(2,3) 1
+set a(3,6) 2</tt></pre>
+</div></div>
+<div class="paragraph"><p>set the elements of <em>a</em> whose indexes are <em>2,3</em> and <em>3,6</em>.</p></div>
+<div class="paragraph"><p>In general, array elements may be used anywhere in Tcl that scalar
+variables may be used.</p></div>
+<div class="paragraph"><p>If an array is defined with a particular name, then there may
+not be a scalar variable with the same name.</p></div>
+<div class="paragraph"><p>Similarly, if there is a scalar variable with a particular
+name then it is not possible to make array references to the
+variable.</p></div>
+<div class="paragraph"><p>To convert a scalar variable to an array or vice versa, remove
+the existing variable with the <em>unset</em> command.</p></div>
+<div class="paragraph"><p>The <em>array</em> command provides several features for dealing
+with arrays, such as querying the names of all the elements of
+the array and converting between an array and a list.</p></div>
+<div class="paragraph"><p>Variables may be either global or local. If a variable
+name is used when a procedure isn’t being executed, then it
+automatically refers to a global variable. Variable names used
+within a procedure normally refer to local variables associated with that
+invocation of the procedure. Local variables are deleted whenever
+a procedure exits. Either <em>global</em> command may be used to request
+that a name refer to a global variable for the duration of the current
+procedure (this is somewhat analogous to <em>extern</em> in C), or the variable
+may be explicitly scoped with the <em>::</em> prefix. For example</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a 1
+set b 2
+proc p {} {
+ set c 3
+ global a</tt></pre>
+</div></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt> puts "$a $::b $c"
+}
+p</tt></pre>
+</div></div>
+<div class="paragraph"><p>will output:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>1 2 3</tt></pre>
+</div></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_arrays_as_lists_in_jim">ARRAYS AS LISTS IN JIM</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Unlike Tcl, Jim can automatically convert between a list (with an even
+number of elements) and an array value. This is similar to the way Tcl
+can convert between a string and a list.</p></div>
+<div class="paragraph"><p>For example:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a {1 one 2 two}
+puts $a(2)</tt></pre>
+</div></div>
+<div class="paragraph"><p>will output:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>two</tt></pre>
+</div></div>
+<div class="paragraph"><p>Thus <em>array set</em> is equivalent to <em>set</em> when the variable does not
+exist or is empty.</p></div>
+<div class="paragraph"><p>The reverse is also true where an array will be converted into
+a list.</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a(1) one; set a(2) two
+puts $a</tt></pre>
+</div></div>
+<div class="paragraph"><p>will output:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>1 one 2 two</tt></pre>
+</div></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_dictionary_values">DICTIONARY VALUES</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Tcl 8.5 introduced the dict command, and Jim Tcl has added a version
+of this command. Dictionaries provide efficient access to key-value
+pairs, just like arrays, but dictionaries are pure values. This
+means that you can pass them to a procedure just as a list or a
+string. Tcl dictionaries are therefore much more like Tcl lists,
+except that they represent a mapping from keys to values, rather
+than an ordered sequence.</p></div>
+<div class="paragraph"><p>You can nest dictionaries, so that the value for a particular key
+consists of another dictionary. That way you can elegantly build
+complicated data structures, such as hierarchical databases. You
+can also combine dictionaries with other Tcl data structures. For
+instance, you can build a list of dictionaries that themselves
+contain lists.</p></div>
+<div class="paragraph"><p>Dictionaries are values that contain an efficient, order-preserving
+mapping from arbitrary keys to arbitrary values. Each key in the
+dictionary maps to a single value. They have a textual format that
+is exactly that of any list with an even number of elements, with
+each mapping in the dictionary being represented as two items in
+the list. When a command takes a dictionary and produces a new
+dictionary based on it (either returning it or writing it back into
+the variable that the starting dictionary was read from) the new
+dictionary will have the same order of keys, modulo any deleted
+keys and with new keys added on to the end. When a string is
+interpreted as a dictionary and it would otherwise have duplicate
+keys, only the last value for a particular key is used; the others
+are ignored, meaning that, "apple banana" and "apple carrot apple
+banana" are equivalent dictionaries (with different string
+representations).</p></div>
+<div class="paragraph"><p>Note that in Jim, arrays are implemented as dictionaries.
+Thus automatic conversion between lists and dictionaries applies
+as it does for arrays.</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>jim> dict set a 1 one
+1 one
+jim> dict set a 2 two
+1 one 2 two
+jim> puts $a
+1 one 2 two
+jim> puts $a(2)
+two
+jim> dict set a 3 T three
+1 one 2 two 3 {T three}</tt></pre>
+</div></div>
+<div class="paragraph"><p>See the <em>dict</em> command for more details.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_garbage_collection_references_lambda">GARBAGE COLLECTION, REFERENCES, LAMBDA</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Unlike Tcl, Jim has some sophistocated support for functional programming.
+These are described briefly below.</p></div>
+<div class="paragraph"><p>More information may be found at <a href="http://wiki.tcl.tk/13847">http://wiki.tcl.tk/13847</a></p></div>
+<div class="sect2">
+<h3 id="_references">References</h3>
+<div class="paragraph"><p>A reference can be thought of as holding a value with one level of indirection,
+where the value may be garbage collected when unreferenced.
+Consider the following example:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>jim> set r [ref "One String" test]
+<reference.<test___>.00000000000000000000>
+jim> getref $r
+One String</tt></pre>
+</div></div>
+<div class="paragraph"><p>The operation <em>ref</em> creates a references to the value specfied by the
+first argument. (The second argument is a "type" used for documentation purposes).</p></div>
+<div class="paragraph"><p>The operation <em>getref</em> is the dereferencing operation which retrieves the value
+stored in the reference.</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>jim> setref $r "New String"
+New String
+jim> getref $r
+New String</tt></pre>
+</div></div>
+<div class="paragraph"><p>The operation <em>setref</em> replaces the value stored by the reference. If the old value
+is no longer accessible by any reference, it will eventually be automatically be garbage
+collected.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_garbage_collection">Garbage Collection</h3>
+<div class="paragraph"><p>Normally, all values in Tcl are passed by value. As such values are copied and released
+automatically as necessary.</p></div>
+<div class="paragraph"><p>With the introduction of references, it is possible to create values whose lifetime
+transcend their scope. To support this, case, the Jim system will periodically identify
+and discard objects which are no longer accessible by any reference.</p></div>
+<div class="paragraph"><p>The <em>collect</em> command may be used to force garbage collection. Consider a reference created
+with a finalizer:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>jim> proc f {ref value} { puts "Finaliser called for $ref,$value" }
+jim> set r [ref "One String" test f]
+<reference.<test___>.00000000000
+jim> collect
+0
+jim> set r ""
+jim> collect
+Finaliser called for <reference.<test___>.00000000000,One String
+1</tt></pre>
+</div></div>
+<div class="paragraph"><p>Note that once the reference, <em>r</em>, was modified so that it no longer
+contained a reference to the value, the garbage collector discarded
+the value (after calling the finalizer).</p></div>
+<div class="paragraph"><p>The finalizer for a reference may be examined or changed with the <em>finalize</em> command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>jim> finalize $r
+f
+jim> finalize $r newf
+newf</tt></pre>
+</div></div>
+</div>
+<div class="sect2">
+<h3 id="_lambda">Lambda</h3>
+<div class="paragraph"><p>Jim provides a garbage collected lambda function. This is a procedure
+which is able to create an anonymous procedure. Consider:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>jim> set f [lambda {a} {{x 0}} { incr x $a }]
+jim> $f 1
+1
+jim> $f 2
+3
+jim> set f ""</tt></pre>
+</div></div>
+<div class="paragraph"><p>This create an anonymous procedure (with the name stored in <em>f</em>), with a static variable
+which is incremented by the supplied value and the result returned.</p></div>
+<div class="paragraph"><p>Once the procedure name is no longer accessible, it will automatically be deleted
+when the garbage collector runs.</p></div>
+<div class="paragraph"><p>The procedure may also be delete immediately by renaming it "". e.g.</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>jim> rename $f ""</tt></pre>
+</div></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_built_in_commands">BUILT-IN COMMANDS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>The Tcl library provides the following built-in commands, which will
+be available in any application using Tcl. In addition to these
+built-in commands, there may be additional commands defined by each
+application, plus commands defined as Tcl procedures.</p></div>
+<div class="paragraph"><p>In the command syntax descriptions below, words in <tt><strong>boldface</strong></tt> are
+literals that you type verbatim to Tcl.</p></div>
+<div class="paragraph"><p>Words in <tt><em>italics</em></tt> are meta-symbols; they serve as names for any of
+a range of values that you can type.</p></div>
+<div class="paragraph"><p>Optional arguments or groups of arguments are indicated by enclosing them
+in <tt>?question-marks?</tt>.</p></div>
+<div class="paragraph"><p>Ellipses (<tt>…</tt>) indicate that any number of additional
+arguments or groups of arguments may appear, in the same format
+as the preceding argument(s).</p></div>
+<div class="sect2">
+<h3 id="CommandIndex">Command Index</h3>
+</div>
+<div class="sect2">
+<h3 id="_alarm">alarm</h3>
+<div class="paragraph"><p><tt><strong>alarm</strong> <em>seconds</em></tt></p></div>
+<div class="paragraph"><p>Delivers the <em>SIGALRM</em> signal to the process after the given
+number of seconds. If the platform supports <em>ularm(3)</em> then
+the argument may be a floating point value. Otherwise it must
+be an integer.</p></div>
+<div class="paragraph"><p>Note that unless a signal handler for <em>SIGALRM</em> has been installed
+(see <em>signal</em>), the process will exit on this signal.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_alias">alias</h3>
+<div class="paragraph"><p><tt><strong>alias</strong> <em>name args…</em></tt></p></div>
+<div class="paragraph"><p>Creates a single word alias (proc) for one or more words. For example,
+the following creates an alias for the command <em>info exists</em>.</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>alias e info exists
+if {[e var]} {
+ ...
+}</tt></pre>
+</div></div>
+<div class="paragraph"><p><em>alias</em> returns <strong>name</strong>, allowing it to be used with 'local.</p></div>
+<div class="paragraph"><p>See also <em>proc</em>, <em>curry</em>, <em>lambda</em>, <em>local</em>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_append">append</h3>
+<div class="paragraph"><p><tt><strong>append</strong> <em>varName value ?value value …?</em></tt></p></div>
+<div class="paragraph"><p>Append all of the <strong>value</strong> arguments to the current value
+of variable <strong>varName</strong>. If <strong>varName</strong> doesn’t exist,
+it is given a value equal to the concatenation of all the
+<strong>value</strong> arguments.</p></div>
+<div class="paragraph"><p>This command provides an efficient way to build up long
+variables incrementally.
+For example, <em>append a $b</em> is much more efficient than
+<em>set a $a$b</em> if <em>$a</em> is long.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_array">array</h3>
+<div class="paragraph"><p><tt><strong>array</strong> <em>option arrayName ?arg arg …?</em></tt></p></div>
+<div class="paragraph"><p>This command performs one of several operations on the
+variable given by <strong>arrayName</strong>.</p></div>
+<div class="paragraph"><p>Note that in general, if the named array does not exist, the <strong>array</strong> command behaves
+as though the array exists but is empty.</p></div>
+<div class="paragraph"><p>The <strong>option</strong> argument determines what action is carried out by the
+command. The legal <strong>options</strong> (which may be abbreviated) are:</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt><strong>array exists</strong> <em>arrayName</em></tt>
+</dt>
+<dd>
+<p>
+ Returns 1 if arrayName is an array variable, 0 if there is
+ no variable by that name. This command is essentially
+ identical to <em>info exists</em>
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>array get</strong> <em>arrayName ?pattern?</em></tt>
+</dt>
+<dd>
+<p>
+ Returns a list containing pairs of elements. The first
+ element in each pair is the name of an element in arrayName
+ and the second element of each pair is the value of the
+ array element. The order of the pairs is undefined. If
+ pattern is not specified, then all of the elements of the
+ array are included in the result. If pattern is specified,
+ then only those elements whose names match pattern (using
+ the matching rules of string match) are included. If arrayName
+ isn’t the name of an array variable, or if the array contains
+ no elements, then an empty list is returned.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>array names</strong> <em>arrayName ?pattern?</em></tt>
+</dt>
+<dd>
+<p>
+ Returns a list containing the names of all of the elements
+ in the array that match pattern. If pattern is omitted then
+ the command returns all of the element names in the array.
+ If pattern is specified, then only those elements whose
+ names match pattern (using the matching rules of string
+ match) are included. If there are no (matching) elements
+ in the array, or if arrayName isn’t the name of an array
+ variable, then an empty string is returned.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>array set</strong> <em>arrayName list</em></tt>
+</dt>
+<dd>
+<p>
+ Sets the values of one or more elements in arrayName. list
+ must have a form like that returned by array get, consisting
+ of an even number of elements. Each odd-numbered element
+ in list is treated as an element name within arrayName, and
+ the following element in list is used as a new value for
+ that array element. If the variable arrayName does not
+ already exist and list is empty, arrayName is created with
+ an empty array value.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>array size</strong> <em>arrayName</em></tt>
+</dt>
+<dd>
+<p>
+ Returns the number of elements in the array. If arrayName
+ isn’t the name of an array then 0 is returned.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>array unset</strong> <em>arrayName ?pattern?</em></tt>
+</dt>
+<dd>
+<p>
+ Unsets all of the elements in the array that match pattern
+ (using the matching rules of string match). If arrayName
+ isn’t the name of an array variable or there are no matching
+ elements in the array, no error will be raised. If pattern
+ is omitted and arrayName is an array variable, then the
+ command unsets the entire array. The command always returns
+ an empty string.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_break">break</h3>
+<div class="paragraph"><p><tt><strong>break</strong></tt></p></div>
+<div class="paragraph"><p>This command may be invoked only inside the body of a loop command
+such as <em>for</em> or <em>foreach</em> or <em>while</em>. It returns a <tt>JIM_BREAK</tt> code
+to signal the innermost containing loop command to return immediately.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_case">case</h3>
+<div class="paragraph"><p><tt><strong>case</strong> <em>string</em> ?<strong>in</strong>? <em>patList body ?patList body …?</em></tt></p></div>
+<div class="paragraph"><p><tt><strong>case</strong> <em>string</em> ?<strong>in</strong>? {<em>patList body ?patList body …?</em>}</tt></p></div>
+<div class="paragraph"><p><strong>Note</strong> that the switch command should generally be preferred unless compatibility
+with Tcl 6.x is desired.</p></div>
+<div class="paragraph"><p>Match <strong>string</strong> against each of the <strong>patList</strong> arguments
+in order. If one matches, then evaluate the following <strong>body</strong> argument
+by passing it recursively to the Tcl interpreter, and return the result
+of that evaluation. Each <strong>patList</strong> argument consists of a single
+pattern or list of patterns. Each pattern may contain any of the wild-cards
+described under <em>string match</em>.</p></div>
+<div class="paragraph"><p>If a <strong>patList</strong> argument is <em>default</em>, the corresponding body will be
+evaluated if no <strong>patList</strong> matches <strong>string</strong>. If no <strong>patList</strong> argument
+matches <strong>string</strong> and no default is given, then the <em>case</em> command returns
+an empty string.</p></div>
+<div class="paragraph"><p>Two syntaxes are provided.</p></div>
+<div class="paragraph"><p>The first uses a separate argument for each of the patterns and commands;
+this form is convenient if substitutions are desired on some of the
+patterns or commands.</p></div>
+<div class="paragraph"><p>The second form places all of the patterns and commands together into
+a single argument; the argument must have proper list structure, with
+the elements of the list being the patterns and commands.</p></div>
+<div class="paragraph"><p>The second form makes it easy to construct multi-line case commands,
+since the braces around the whole list make it unnecessary to include a
+backslash at the end of each line.</p></div>
+<div class="paragraph"><p>Since the <strong>patList</strong> arguments are in braces in the second form,
+no command or variable substitutions are performed on them; this makes
+the behavior of the second form different than the first form in some
+cases.</p></div>
+<div class="paragraph"><p>Below are some examples of <em>case</em> commands:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>case abc in {a b} {format 1} default {format 2} a* {format 3}</tt></pre>
+</div></div>
+<div class="paragraph"><p>will return <em>3</em>,</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>case a in {
+ {a b} {format 1}
+ default {format 2}
+ a* {format 3}
+}</tt></pre>
+</div></div>
+<div class="paragraph"><p>will return <em>1</em>, and</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>case xyz {
+ {a b}
+ {format 1}
+ default
+ {format 2}
+ a*
+ {format 3}
+}</tt></pre>
+</div></div>
+<div class="paragraph"><p>will return <em>2</em>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_catch">catch</h3>
+<div class="paragraph"><p><tt><strong>catch</strong> <em>?-?no?code …?</em> <strong>?--?</strong> <em>command ?resultVarName? ?optionsVarName?</em></tt></p></div>
+<div class="paragraph"><p>The <em>catch</em> command may be used to prevent errors from aborting
+command interpretation. <em>Catch</em> evalues <strong>command</strong>, and returns a
+<tt>JIM_OK</tt> code, regardless of any errors that might occur while
+executing <strong>command</strong> (with the possible exception of <tt>JIM_SIGNAL</tt> -
+see below).</p></div>
+<div class="paragraph"><p>The return value from <em>catch</em> is a decimal string giving the code
+returned by the Tcl interpreter after executing <strong>command</strong>. This
+will be <em>0</em> (<tt>JIM_OK</tt>) if there were no errors in <strong>command</strong>; otherwise
+it will have a non-zero value corresponding to one of the exceptional
+return codes (see jim.h for the definitions of code values, or the
+<em>info returncodes</em> command).</p></div>
+<div class="paragraph"><p>If the <strong>resultVarName</strong> argument is given, then it gives the name
+of a variable; <em>catch</em> will set the value of the variable to the
+string returned from <strong>command</strong> (either a result or an error message).</p></div>
+<div class="paragraph"><p>If the <strong>optionsVarName</strong> argument is given, then it gives the name
+of a variable; <em>catch</em> will set the value of the variable to a
+dictionary. For any return code other than <tt>JIM_RETURN</tt>, the value
+for the key <tt>-code</tt> will be set to the return code. For <tt>JIM_RETURN</tt>
+it will be set to the code given in <em>return -code</em>. Additionally,
+for the return code <tt>JIM_ERR</tt>, the value of the key <tt>-errorinfo</tt>
+will contain the current stack trace (the same result as <em>info
+stacktrace</em>), the value of the key <tt>-errorcode</tt> will contain the
+same value as the global variable $::errorCode, and the value of
+the key <tt>-level</tt> will be the current return level (see <em>return
+-level</em>). This can be useful to rethrow an error:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>if {[catch {...} msg opts]} {
+ ...maybe do something with the error...
+ incr opts(-level)
+ return {*}$opts $msg
+}</tt></pre>
+</div></div>
+<div class="paragraph"><p>Normally <em>catch</em> will <strong>not</strong> catch any of the codes <tt>JIM_EXIT</tt>, <tt>JIM_EVAL</tt> or <tt>JIM_SIGNAL</tt>.
+The set of codes which will be caught may be modified by specifying the one more codes before
+<strong>command</strong>.</p></div>
+<div class="paragraph"><p>e.g. To catch <tt>JIM_EXIT</tt> but not <tt>JIM_BREAK</tt> or <tt>JIM_CONTINUE</tt></p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>catch -exit -nobreak -nocontinue -- { ... }</tt></pre>
+</div></div>
+<div class="paragraph"><p>The use of <tt>--</tt> is optional. It signifies that no more return code options follow.</p></div>
+<div class="paragraph"><p>Note that if a signal marked as <em>signal handle</em> is caught with <em>catch -signal</em>, the return value
+(stored in <strong>resultVarName</strong>) is name of the signal caught.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_cd">cd</h3>
+<div class="paragraph"><p><tt><strong>cd</strong> <em>dirName</em></tt></p></div>
+<div class="paragraph"><p>Change the current working directory to <strong>dirName</strong>.</p></div>
+<div class="paragraph"><p>Returns an empty string.</p></div>
+<div class="paragraph"><p>This command can potentially be disruptive to an application, so it may
+be removed in some applications.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_clock">clock</h3>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt><strong>clock seconds</strong></tt>
+</dt>
+<dd>
+<p>
+ Returns the current time as seconds since the epoch.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>clock format</strong> <em>seconds</em> ?<strong>-format</strong> <em>format?</em></tt>
+</dt>
+<dd>
+<p>
+ Format the given time (seconds since the epoch) according to the given
+ format. See strftime(3) for supported formats.
+ If no format is supplied, "%c" is used.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>clock scan</strong> <em>str</em> <strong>-format</strong> <em>format</em></tt>
+</dt>
+<dd>
+<p>
+ Scan the given time string using the given format string.
+ See strptime(3) for supported formats.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_close">close</h3>
+<div class="paragraph"><p><tt><strong>close</strong> <em>fileId</em></tt></p></div>
+<div class="paragraph"><p><tt><em>fileId</em> <strong>close</strong></tt></p></div>
+<div class="paragraph"><p>Closes the file given by <strong>fileId</strong>.
+<strong>fileId</strong> must be the return value from a previous invocation
+of the <em>open</em> command; after this command, it should not be
+used anymore.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_collect">collect</h3>
+<div class="paragraph"><p><tt><strong>collect</strong></tt></p></div>
+<div class="paragraph"><p>Normally reference garbage collection is automatically performed periodically.
+However it may be run immediately with the <em>collect</em> command.</p></div>
+<div class="paragraph"><p>See GARBAGE COLLECTION, REFERENCES, LAMBDA for more detail.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_concat">concat</h3>
+<div class="paragraph"><p><tt><strong>concat</strong> <em>arg ?arg …?</em></tt></p></div>
+<div class="paragraph"><p>This command treats each argument as a list and concatenates them
+into a single list. It permits any number of arguments. For example,
+the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>concat a b {c d e} {f {g h}}</tt></pre>
+</div></div>
+<div class="paragraph"><p>will return</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>a b c d e f {g h}</tt></pre>
+</div></div>
+<div class="paragraph"><p>as its result.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_continue">continue</h3>
+<div class="paragraph"><p><tt><strong>continue</strong></tt></p></div>
+<div class="paragraph"><p>This command may be invoked only inside the body of a loop command such
+as <em>for</em> or <em>foreach</em> or <em>while</em>. It returns a <tt>JIM_CONTINUE</tt> code to
+signal the innermost containing loop command to skip the remainder of
+the loop’s body but continue with the next iteration of the loop.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_curry">curry</h3>
+<div class="paragraph"><p><tt><strong>alias</strong> <em>args…</em></tt></p></div>
+<div class="paragraph"><p>Similar to <em>alias</em> except it creates an anonymous procedure (lambda) instead of
+a named procedure.</p></div>
+<div class="paragraph"><p>the following creates a local, unnamed alias for the command <em>info exists</em>.</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set e [local curry info exists]
+if {[$e var]} {
+ ...
+}</tt></pre>
+</div></div>
+<div class="paragraph"><p><em>curry</em> returns the name of the procedure.</p></div>
+<div class="paragraph"><p>See also <em>proc</em>, <em>alias</em>, <em>lambda</em>, <em>local</em>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_dict">dict</h3>
+<div class="paragraph"><p><tt><strong>dict</strong> <em>option ?arg arg …?</em></tt></p></div>
+<div class="paragraph"><p>Performs one of several operations on dictionary values.</p></div>
+<div class="paragraph"><p>The <strong>option</strong> argument determines what action is carried out by the
+command. The legal <strong>options</strong> are:</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<strong>dict create</strong> <em>?key value …?</em>+
+</dt>
+<dd>
+<p>
+ Create and return a new dictionary value that contains each of
+ the key/value mappings listed as arguments (keys and values
+ alternating, with each key being followed by its associated
+ value.)
+</p>
+</dd>
+<dt class="hdlist1">
+<strong>dict exists</strong> <em>dictionary key ?key …?</em>+
+</dt>
+<dd>
+<p>
+ Returns a boolean value indicating whether the given key (or path
+ of keys through a set of nested dictionaries) exists in the given
+ dictionary value. This returns a true value exactly when <em>dict get</em>
+ on that path will succeed.
+</p>
+</dd>
+<dt class="hdlist1">
+<strong>dict get</strong> <em>dictionary ?key …?</em>+
+</dt>
+<dd>
+<p>
+ Given a dictionary value (first argument) and a key (second argument),
+ this will retrieve the value for that key. Where several keys are
+ supplied, the behaviour of the command shall be as if the result
+ of <em>dict get $dictVal $key</em> was passed as the first argument to
+ dict get with the remaining arguments as second (and possibly
+ subsequent) arguments. This facilitates lookups in nested dictionaries.
+ If no keys are provided, dict would return a list containing pairs
+ of elements in a man- ner similar to array get. That is, the first
+ element of each pair would be the key and the second element would
+ be the value for that key. It is an error to attempt to retrieve
+ a value for a key that is not present in the dictionary.
+</p>
+</dd>
+<dt class="hdlist1">
+<strong>dict set</strong> <em>dictionaryName key ?key …? value</em>+
+</dt>
+<dd>
+<p>
+ This operation takes the <strong>name</strong> of a variable containing a dictionary
+ value and places an updated dictionary value in that variable
+ containing a mapping from the given key to the given value. When
+ multiple keys are present, this operation creates or updates a chain
+ of nested dictionaries.
+</p>
+</dd>
+<dt class="hdlist1">
+<strong>dict unset</strong> <em>dictionaryName key ?key …? value</em>+
+</dt>
+<dd>
+<p>
+ This operation (the companion to <em>dict set</em>) takes the name of a
+ variable containing a dictionary value and places an updated
+ dictionary value in that variable that does not contain a mapping
+ for the given key. Where multiple keys are present, this describes
+ a path through nested dictionaries to the mapping to remove. At
+ least one key must be specified, but the last key on the key-path
+ need not exist. All other components on the path must exist.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_env">env</h3>
+<div class="paragraph"><p><tt><strong>env</strong> <em>?name? ?default?</em></tt></p></div>
+<div class="paragraph"><p>If <strong>name</strong> is supplied, returns the value of <strong>name</strong> from the initial
+environment (see getenv(3)). An error is returned if <strong>name</strong> does not
+exist in the environment, unless <strong>default</strong> is supplied - in which case
+that value is returned instead.</p></div>
+<div class="paragraph"><p>If no arguments are supplied, returns a list of all environment variables
+and their values as <tt>{name value …}</tt></p></div>
+<div class="paragraph"><p>See also the global variable <em>::env</em></p></div>
+</div>
+<div class="sect2">
+<h3 id="_eof">eof</h3>
+<div class="paragraph"><p><tt><strong>eof</strong> <em>fileId</em></tt></p></div>
+<div class="paragraph"><p><tt><em>fileId</em> <strong>eof</strong></tt></p></div>
+<div class="paragraph"><p>Returns 1 if an end-of-file condition has occurred on <strong>fileId</strong>,
+0 otherwise.</p></div>
+<div class="paragraph"><p><strong>fileId</strong> must have been the return value from a previous call to <em>open</em>,
+or it may be <em>stdin</em>, <em>stdout</em>, or <em>stderr</em> to refer to one of the
+standard I/O channels.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_error">error</h3>
+<div class="paragraph"><p><tt><strong>error</strong> <em>message ?stacktrace?</em></tt></p></div>
+<div class="paragraph"><p>Returns a <tt>JIM_ERR</tt> code, which causes command interpretation to be
+unwound. <strong>message</strong> is a string that is returned to the application
+to indicate what went wrong.</p></div>
+<div class="paragraph"><p>If the <strong>stacktrace</strong> argument is provided and is non-empty,
+it is used to initialize the stacktrace.</p></div>
+<div class="paragraph"><p>This feature is most useful in conjunction with the <em>catch</em> command:
+if a caught error cannot be handled successfully, <strong>stacktrace</strong> can be used
+to return a stack trace reflecting the original point of occurrence
+of the error:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>catch {...} errMsg
+...
+error $errMsg [info stacktrace]</tt></pre>
+</div></div>
+<div class="paragraph"><p>See also <em>errorInfo</em>, <em>info stacktrace</em>, <em>catch</em> and <em>return</em></p></div>
+</div>
+<div class="sect2">
+<h3 id="_errorinfo">errorInfo</h3>
+<div class="paragraph"><p><tt><strong>errorInfo</strong> <em>error ?stacktrace?</em></tt></p></div>
+<div class="paragraph"><p>Returns a human-readable representation of the given error message and stack trace.
+Typical usage is:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>if {[catch {...} error]} {
+ puts stderr [errorInfo $error [info stacktrace]]
+ exit 1
+}</tt></pre>
+</div></div>
+<div class="paragraph"><p>See also <em>error</em>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_eval">eval</h3>
+<div class="paragraph"><p><tt><strong>eval</strong> <em>arg ?arg …?</em></tt></p></div>
+<div class="paragraph"><p><em>eval</em> takes one or more arguments, which together comprise a Tcl
+command (or collection of Tcl commands separated by newlines in the
+usual way). <em>eval</em> concatenates all its arguments in the same
+fashion as the <em>concat</em> command, passes the concatenated string to the
+Tcl interpreter recursively, and returns the result of that
+evaluation (or any error generated by it).</p></div>
+</div>
+<div class="sect2">
+<h3 id="_exec">exec</h3>
+<div class="paragraph"><p><tt><strong>exec</strong> <em>arg ?arg …?</em></tt></p></div>
+<div class="paragraph"><p>This command treats its arguments as the specification
+of one or more UNIX commands to execute as subprocesses.
+The commands take the form of a standard shell pipeline;
+<em>|</em> arguments separate commands in the
+pipeline and cause standard output of the preceding command
+to be piped into standard input of the next command (or <em>|&</em> for
+both standard output and standard error).</p></div>
+<div class="paragraph"><p>Under normal conditions the result of the <em>exec</em> command
+consists of the standard output produced by the last command
+in the pipeline.</p></div>
+<div class="paragraph"><p>If any of the commands in the pipeline exit abnormally or
+are killed or suspended, then <em>exec</em> will return an error
+and the error message will include the pipeline’s output followed by
+error messages describing the abnormal terminations.</p></div>
+<div class="paragraph"><p>If any of the commands writes to its standard error file,
+then <em>exec</em> will return an error, and the error message
+will include the pipeline’s output, followed by messages
+about abnormal terminations (if any), followed by the standard error
+output.</p></div>
+<div class="paragraph"><p>If the last character of the result or error message
+is a newline then that character is deleted from the result
+or error message for consistency with normal
+Tcl return values.</p></div>
+<div class="paragraph"><p>An <strong>arg</strong> may have one of the following special forms:</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt>>filename</tt>
+</dt>
+<dd>
+<p>
+ The standard output of the last command in the pipeline
+ is redirected to the file. In this situation <em>exec</em>
+ will normally return an empty string.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>>>filename</tt>
+</dt>
+<dd>
+<p>
+ As above, but append to the file.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>>@fileId</tt>
+</dt>
+<dd>
+<p>
+ The standard output of the last command in the pipeline is
+ redirected to the given (writable) file descriptor (e.g. stdout,
+ stderr, or the result of <em>open</em>). In this situation <em>exec</em>
+ will normally return an empty string.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>2>filename</tt>
+</dt>
+<dd>
+<p>
+ The standard error of the last command in the pipeline
+ is redirected to the file.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>2>>filename</tt>
+</dt>
+<dd>
+<p>
+ As above, but append to the file.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>2>@fileId</tt>
+</dt>
+<dd>
+<p>
+ The standard error of the last command in the pipeline is
+ redirected to the given (writable) file descriptor.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>2>@1</tt>
+</dt>
+<dd>
+<p>
+ The standard error of the last command in the pipeline is
+ redirected to the same file descriptor as the standard output.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>>&filename</tt>
+</dt>
+<dd>
+<p>
+ Both the standard output and standard error of the last command
+ in the pipeline is redirected to the file.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>>>&filename</tt>
+</dt>
+<dd>
+<p>
+ As above, but append to the file.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><filename</tt>
+</dt>
+<dd>
+<p>
+ The standard input of the first command in the pipeline
+ is taken from the file.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><<string</tt>
+</dt>
+<dd>
+<p>
+ The standard input of the first command is taken as the
+ given immediate value.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><@fileId</tt>
+</dt>
+<dd>
+<p>
+ The standard input of the first command in the pipeline
+ is taken from the given (readable) file descriptor.
+</p>
+</dd>
+</dl></div>
+<div class="paragraph"><p>If there is no redirection of standard input, standard error
+or standard output, these are connected to the corresponding
+input or output of the application.</p></div>
+<div class="paragraph"><p>If the last <strong>arg</strong> is <em>&</em> then the command will be
+executed in background.
+In this case the standard output from the last command
+in the pipeline will
+go to the application’s standard output unless
+redirected in the command, and error output from all
+the commands in the pipeline will go to the application’s
+standard error file. The return value of exec in this case
+is a list of process ids (pids) in the pipeline.</p></div>
+<div class="paragraph"><p>Each <strong>arg</strong> becomes one word for a command, except for
+<em>|</em>, <em><</em>, <em><<</em>, <em>></em>, and <em>&</em> arguments, and the
+arguments that follow <em><</em>, <em><<</em>, and <em>></em>.</p></div>
+<div class="paragraph"><p>The first word in each command is taken as the command name;
+the directories in the PATH environment variable are searched for
+an executable by the given name.</p></div>
+<div class="paragraph"><p>No <em>glob</em> expansion or other shell-like substitutions
+are performed on the arguments to commands.</p></div>
+<div class="paragraph"><p>If the command fails, the global $::errorCode (and the -errorcode
+option in <em>catch</em>) will be set to a list, as follows:</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt><strong>CHILDKILLED</strong> <em>pid sigName msg</em></tt>
+</dt>
+<dd>
+<p>
+ This format is used when a child process has been killed
+ because of a signal. The pid element will be the process’s
+ identifier (in decimal). The sigName element will be the
+ symbolic name of the signal that caused the process to
+ terminate; it will be one of the names from the include
+ file signal.h, such as SIGPIPE. The msg element will be a
+ short human-readable message describing the signal, such
+ as "write on pipe with no readers" for SIGPIPE.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>CHILDSUSP</strong> <em>pid sigName msg</em></tt>
+</dt>
+<dd>
+<p>
+ This format is used when a child process has been suspended
+ because of a signal. The pid element will be the process’s
+ identifier, in decimal. The sigName element will be the
+ symbolic name of the signal that caused the process to
+ suspend; this will be one of the names from the include
+ file signal.h, such as SIGTTIN. The msg element will be a
+ short human-readable message describing the signal, such
+ as "background tty read" for SIGTTIN.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>CHILDSTATUS</strong> <em>pid code</em></tt>
+</dt>
+<dd>
+<p>
+ This format is used when a child process has exited with a
+ non-zero exit status. The pid element will be the process’s
+ identifier (in decimal) and the code element will be the
+ exit code returned by the process (also in decimal).
+</p>
+</dd>
+</dl></div>
+<div class="paragraph"><p>The environment for the executed command is set from $::env (unless
+this variable is unset, in which case the original environment is used).</p></div>
+</div>
+<div class="sect2">
+<h3 id="_exit">exit</h3>
+<div class="paragraph"><p><tt><strong>exit</strong> <em>?returnCode?</em></tt></p></div>
+<div class="paragraph"><p>Terminate the process, returning <strong>returnCode</strong> to the
+parent as the exit status.</p></div>
+<div class="paragraph"><p>If <strong>returnCode</strong> isn’t specified then it defaults
+to 0.</p></div>
+<div class="paragraph"><p>Note that exit can be caught with <strong>catch</strong>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_expr">expr</h3>
+<div class="paragraph"><p><tt><strong>expr</strong> <em>arg</em></tt></p></div>
+<div class="paragraph"><p>Calls the expression processor to evaluate <strong>arg</strong>, and returns
+the result as a string. See the section EXPRESSIONS above.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_file">file</h3>
+<div class="paragraph"><p><tt><strong>file</strong> <em>option name ?arg arg …?</em></tt></p></div>
+<div class="paragraph"><p>Operate on a file or a file name. <strong>name</strong> is the name of a file.</p></div>
+<div class="paragraph"><p><strong>Option</strong> indicates what to do with the file name. Any unique
+abbreviation for <strong>option</strong> is acceptable. The valid options are:</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt><strong>file atime</strong> <em>name</em></tt>
+</dt>
+<dd>
+<p>
+ Return a decimal string giving the time at which file <strong>name</strong>
+ was last accessed. The time is measured in the standard UNIX
+ fashion as seconds from a fixed starting time (often January 1, 1970).
+ If the file doesn’t exist or its access time cannot be queried then an
+ error is generated.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file copy ?-force?</strong> <em>source target</em></tt>
+</dt>
+<dd>
+<p>
+ Copies file <strong>source</strong> to file <strong>target</strong>. The source file must exist.
+ The target file must not exist, unless <strong>-force</strong> is specified.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file delete</strong> <em>name …</em></tt>
+</dt>
+<dd>
+<p>
+ Deletes file or directory <strong>name</strong>. If the file or directory doesn’t exist, nothing happens.
+ If it can’t be deleted, an error is generated. Non-empty directories will not be deleted.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file dirname</strong> <em>name</em></tt>
+</dt>
+<dd>
+<p>
+ Return all of the characters in <strong>name</strong> up to but not including
+ the last slash character. If there are no slashes in <strong>name</strong>
+ then return <em>.</em> (a single dot). If the last slash in <strong>name</strong> is its first
+ character, then return <em>/</em>.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file executable</strong> <em>name</em></tt>
+</dt>
+<dd>
+<p>
+ Return <em>1</em> if file <strong>name</strong> is executable by
+ the current user, <em>0</em> otherwise.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file exists</strong> <em>name</em></tt>
+</dt>
+<dd>
+<p>
+ Return <em>1</em> if file <strong>name</strong> exists and the current user has
+ search privileges for the directories leading to it, <em>0</em> otherwise.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file extension</strong> <em>name</em></tt>
+</dt>
+<dd>
+<p>
+ Return all of the characters in <strong>name</strong> after and including the
+ last dot in <strong>name</strong>. If there is no dot in <strong>name</strong> then return
+ the empty string.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file isdirectory</strong> <em>name</em></tt>
+</dt>
+<dd>
+<p>
+ Return <em>1</em> if file <strong>name</strong> is a directory,
+ <em>0</em> otherwise.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file isfile</strong> <em>name</em></tt>
+</dt>
+<dd>
+<p>
+ Return <em>1</em> if file <strong>name</strong> is a regular file,
+ <em>0</em> otherwise.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file join</strong> <em>arg arg …</em></tt>
+</dt>
+<dd>
+<p>
+ Joins multiple path components. Note that if any components is
+ an absolute path, the preceding components are ignored.
+ Thus <em>file join /tmp /root</em> returns <em>/root</em>.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file lstat</strong> <em>name varName</em></tt>
+</dt>
+<dd>
+<p>
+ Same as <em>stat</em> option (see below) except uses the <strong>lstat</strong>
+ kernel call instead of <strong>stat</strong>. This means that if <strong>name</strong>
+ refers to a symbolic link the information returned in <strong>varName</strong>
+ is for the link rather than the file it refers to. On systems that
+ don’t support symbolic links this option behaves exactly the same
+ as the <em>stat</em> option.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file mkdir</strong> <em>dir1 ?dir2? …</em></tt>
+</dt>
+<dd>
+<p>
+ Creates each directory specified. For each pathname <strong>dir</strong> specified,
+ this command will create all non-existing parent directories
+ as well as <strong>dir</strong> itself. If an existing directory is specified,
+ then no action is taken and no error is returned. Trying to
+ overwrite an existing file with a directory will result in an
+ error. Arguments are processed in the order specified, halting
+ at the first error, if any.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file mtime</strong> <em>name</em></tt>
+</dt>
+<dd>
+<p>
+ Return a decimal string giving the time at which file <strong>name</strong>
+ was last modified. The time is measured in the standard UNIX
+ fashion as seconds from a fixed starting time (often January 1, 1970).
+ If the file doesn’t exist or its modified time cannot be queried then an
+ error is generated.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file normalize</strong> <em>name</em></tt>
+</dt>
+<dd>
+<p>
+ Return the normalized path of <strong>name</strong>. See realpath(3).
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file owned</strong> <em>name</em></tt>
+</dt>
+<dd>
+<p>
+ Return <em>1</em> if file <strong>name</strong> is owned by the current user,
+ <em>0</em> otherwise.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file readable</strong> <em>name</em></tt>
+</dt>
+<dd>
+<p>
+ Return <em>1</em> if file <strong>name</strong> is readable by
+ the current user, <em>0</em> otherwise.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file readlink</strong> <em>name</em></tt>
+</dt>
+<dd>
+<p>
+ Returns the value of the symbolic link given by <strong>name</strong> (i.e. the
+ name of the file it points to). If
+ <strong>name</strong> isn’t a symbolic link or its value cannot be read, then
+ an error is returned. On systems that don’t support symbolic links
+ this option is undefined.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file rename</strong> <em>oldname</em> <em>newname</em></tt>
+</dt>
+<dd>
+<p>
+ Renames the file from the old name to the new name.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file rootname</strong> <em>name</em></tt>
+</dt>
+<dd>
+<p>
+ Return all of the characters in <strong>name</strong> up to but not including
+ the last <em>.</em> character in the name. If <strong>name</strong> doesn’t contain
+ a dot, then return <strong>name</strong>.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file size</strong> <em>name</em></tt>
+</dt>
+<dd>
+<p>
+ Return a decimal string giving the size of file <strong>name</strong> in bytes.
+ If the file doesn’t exist or its size cannot be queried then an
+ error is generated.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file stat</strong> <em>name varName</em></tt>
+</dt>
+<dd>
+<p>
+ Invoke the <em>stat</em> kernel call on <strong>name</strong>, and use the
+ variable given by <strong>varName</strong> to hold information returned from
+ the kernel call.
+ <strong>VarName</strong> is treated as an array variable,
+ and the following elements of that variable are set: <em>atime</em>,
+ <em>ctime</em>, <em>dev</em>, <em>gid</em>, <em>ino</em>, <em>mode</em>, <em>mtime</em>,
+ <em>nlink</em>, <em>size</em>, <em>type</em>, <em>uid</em>.
+ Each element except <em>type</em> is a decimal string with the value of
+ the corresponding field from the <em>stat</em> return structure; see the
+ manual entry for <em>stat</em> for details on the meanings of the values.
+ The <em>type</em> element gives the type of the file in the same form
+ returned by the command <em>file type</em>.
+ This command returns an empty string.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file tail</strong> <em>name</em></tt>
+</dt>
+<dd>
+<p>
+ Return all of the characters in <strong>name</strong> after the last slash.
+ If <strong>name</strong> contains no slashes then return <strong>name</strong>.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file tempfile</strong> <em>?template?</em></tt>
+</dt>
+<dd>
+<p>
+ Creates and returns the name of a unique temporary file. If <strong>template</strong> is omitted, a
+ default template will be used to place the file in /tmp. See mkstemp(3) for
+ the format of the template and security concerns.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file type</strong> <em>name</em></tt>
+</dt>
+<dd>
+<p>
+ Returns a string giving the type of file <strong>name</strong>, which will be
+ one of <em>file</em>, <em>directory</em>, <em>characterSpecial</em>,
+ <em>blockSpecial</em>, <em>fifo</em>, <em>link</em>, or <em>socket</em>.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>file writable</strong> <em>name</em></tt>
+</dt>
+<dd>
+<p>
+ Return <em>1</em> if file <strong>name</strong> is writable by
+ the current user, <em>0</em> otherwise.
+</p>
+</dd>
+</dl></div>
+<div class="paragraph"><p>The <em>file</em> commands that return 0/1 results are often used in
+conditional or looping commands, for example:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>if {![file exists foo]} then {error {bad file name}} else {...}</tt></pre>
+</div></div>
+</div>
+<div class="sect2">
+<h3 id="_finalize">finalize</h3>
+<div class="paragraph"><p><tt><strong>finalize</strong> <em>reference ?command?</em></tt></p></div>
+<div class="paragraph"><p>If <strong>command</strong> is omitted, returns the finalizer command for the given reference.</p></div>
+<div class="paragraph"><p>Otherwise, sets a new finalizer command for the given reference. <strong>command</strong> may be
+the empty string to remove the current finalizer.</p></div>
+<div class="paragraph"><p>The reference must be a valid reference create with the <em>ref</em>
+command.</p></div>
+<div class="paragraph"><p>See GARBAGE COLLECTION, REFERENCES, LAMBDA for more detail.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_flush">flush</h3>
+<div class="paragraph"><p><tt><strong>flush</strong> <em>fileId</em></tt></p></div>
+<div class="paragraph"><p><tt><em>fileId</em> <strong>flush</strong></tt></p></div>
+<div class="paragraph"><p>Flushes any output that has been buffered for <strong>fileId</strong>. <strong>fileId</strong> must
+have been the return value from a previous call to <em>open</em>, or it may be
+<em>stdout</em> or <em>stderr</em> to access one of the standard I/O streams; it must
+refer to a file that was opened for writing. This command returns an
+empty string.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_for">for</h3>
+<div class="paragraph"><p><tt><strong>for</strong> <em>start test next body</em></tt></p></div>
+<div class="paragraph"><p><em>For</em> is a looping command, similar in structure to the C <em>for</em> statement.
+The <strong>start</strong>, <strong>next</strong>, and <strong>body</strong> arguments must be Tcl command strings,
+and <strong>test</strong> is an expression string.</p></div>
+<div class="paragraph"><p>The <em>for</em> command first invokes the Tcl interpreter to execute <strong>start</strong>.
+Then it repeatedly evaluates <strong>test</strong> as an expression; if the result is
+non-zero it invokes the Tcl interpreter on <strong>body</strong>, then invokes the Tcl
+interpreter on <strong>next</strong>, then repeats the loop. The command terminates
+when <strong>test</strong> evaluates to 0.</p></div>
+<div class="paragraph"><p>If a <em>continue</em> command is invoked within <strong>body</strong> then any remaining
+commands in the current execution of <strong>body</strong> are skipped; processing
+continues by invoking the Tcl interpreter on <strong>next</strong>, then evaluating
+<strong>test</strong>, and so on.</p></div>
+<div class="paragraph"><p>If a <em>break</em> command is invoked within <strong>body</strong> or <strong>next</strong>, then the <em>for</em>
+command will return immediately.</p></div>
+<div class="paragraph"><p>The operation of <em>break</em> and <em>continue</em> are similar to the corresponding
+statements in C.</p></div>
+<div class="paragraph"><p><em>For</em> returns an empty string.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_foreach">foreach</h3>
+<div class="paragraph"><p><tt><strong>foreach</strong> <em>varName list body</em></tt></p></div>
+<div class="paragraph"><p><tt><strong>foreach</strong> <em>varList list ?varList2 list2 …? body</em></tt></p></div>
+<div class="paragraph"><p>In this command, <strong>varName</strong> is the name of a variable, <strong>list</strong>
+is a list of values to assign to <strong>varName</strong>, and <strong>body</strong> is a
+collection of Tcl commands.</p></div>
+<div class="paragraph"><p>For each field in <strong>list</strong> (in order from left to right),<em>foreach</em> assigns
+the contents of the field to <strong>varName</strong> (as if the <em>lindex</em> command
+had been used to extract the field), then calls the Tcl interpreter to
+execute <strong>body</strong>.</p></div>
+<div class="paragraph"><p>If instead of being a simple name, <strong>varList</strong> is used, multiple assignments
+are made each time through the loop, one for each element of <strong>varList</strong>.</p></div>
+<div class="paragraph"><p>For example, if there are two elements in <strong>varList</strong> and six elements in
+the list, the loop will be executed three times.</p></div>
+<div class="paragraph"><p>If the length of the list doesn’t evenly divide by the number of elements
+in <strong>varList</strong>, the value of the remaining variables in the last iteration
+of the loop are undefined.</p></div>
+<div class="paragraph"><p>The <em>break</em> and <em>continue</em> statements may be invoked inside <strong>body</strong>,
+with the same effect as in the <em>for</em> command.</p></div>
+<div class="paragraph"><p><em>foreach</em> returns an empty string.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_format">format</h3>
+<div class="paragraph"><p><tt><strong>format</strong> <em>formatString ?arg arg …?</em></tt></p></div>
+<div class="paragraph"><p>This command generates a formatted string in the same way as the
+C <em>sprintf</em> procedure (it uses <em>sprintf</em> in its
+implementation). <strong>FormatString</strong> indicates how to format
+the result, using <em>%</em> fields as in <em>sprintf</em>, and the additional
+arguments, if any, provide values to be substituted into the result.</p></div>
+<div class="paragraph"><p>All of the <em>sprintf</em> options are valid; see the <em>sprintf</em>
+man page for details. Each <strong>arg</strong> must match the expected type
+from the <em>%</em> field in <strong>formatString</strong>; the <em>format</em> command
+converts each argument to the correct type (floating, integer, etc.)
+before passing it to <em>sprintf</em> for formatting.</p></div>
+<div class="paragraph"><p>The only unusual conversion is for <em>%c</em>; in this case the argument
+must be a decimal string, which will then be converted to the corresponding
+ASCII character value.</p></div>
+<div class="paragraph"><p><em>Format</em> does backslash substitution on its <strong>formatString</strong>
+argument, so backslash sequences in <strong>formatString</strong> will be handled
+correctly even if the argument is in braces.</p></div>
+<div class="paragraph"><p>The return value from <em>format</em> is the formatted string.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_getref">getref</h3>
+<div class="paragraph"><p><tt><strong>getref</strong> <em>reference</em></tt></p></div>
+<div class="paragraph"><p>Returns the string associated with <strong>reference</strong>. The reference must
+be a valid reference create with the <em>ref</em> command.</p></div>
+<div class="paragraph"><p>See GARBAGE COLLECTION, REFERENCES, LAMBDA for more detail.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_gets">gets</h3>
+<div class="paragraph"><p><tt><strong>gets</strong> <em>fileId ?varName?</em></tt></p></div>
+<div class="paragraph"><p><tt><em>fileId</em> <strong>gets</strong> <em>?varName?</em></tt></p></div>
+<div class="paragraph"><p>Reads the next line from the file given by <strong>fileId</strong> and discards
+the terminating newline character.</p></div>
+<div class="paragraph"><p>If <strong>varName</strong> is specified, then the line is placed in the variable
+by that name and the return value is a count of the number of characters
+read (not including the newline).</p></div>
+<div class="paragraph"><p>If the end of the file is reached before reading
+any characters then -1 is returned and <strong>varName</strong> is set to an
+empty string.</p></div>
+<div class="paragraph"><p>If <strong>varName</strong> is not specified then the return value will be
+the line (minus the newline character) or an empty string if
+the end of the file is reached before reading any characters.</p></div>
+<div class="paragraph"><p>An empty string will also be returned if a line contains no characters
+except the newline, so <em>eof</em> may have to be used to determine
+what really happened.</p></div>
+<div class="paragraph"><p>If the last character in the file is not a newline character, then
+<em>gets</em> behaves as if there were an additional newline character
+at the end of the file.</p></div>
+<div class="paragraph"><p><strong>fileId</strong> must be <em>stdin</em> or the return value from a previous
+call to <em>open</em>; it must refer to a file that was opened
+for reading.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_glob">glob</h3>
+<div class="paragraph"><p><tt><strong>glob</strong> ?<strong>-nocomplain</strong>? <em>pattern ?pattern …?</em></tt></p></div>
+<div class="paragraph"><p>This command performs filename globbing, using csh rules. The returned
+value from <em>glob</em> is the list of expanded filenames.</p></div>
+<div class="paragraph"><p>If <em>-nocomplain</em> is specified as the first argument then an empty
+list may be returned; otherwise an error is returned if the expanded
+list is empty. The <em>-nocomplain</em> argument must be provided
+exactly: an abbreviation will not be accepted.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_global">global</h3>
+<div class="paragraph"><p><tt><strong>global</strong> <em>varName ?varName …?</em></tt></p></div>
+<div class="paragraph"><p>This command is ignored unless a Tcl procedure is being interpreted.
+If so, then it declares each given <strong>varName</strong> to be a global variable
+rather than a local one. For the duration of the current procedure
+(and only while executing in the current procedure), any reference to
+<strong>varName</strong> will be bound to a global variable instead
+of a local one.</p></div>
+<div class="paragraph"><p>An alternative to using <em>global</em> is to use the <em>::</em> prefix
+to explicitly name a variable in the global scope.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_if">if</h3>
+<div class="paragraph"><p><tt><strong>if</strong> <em>expr1</em> ?<strong>then</strong>? <em>body1</em> <strong>elseif</strong> <em>expr2</em> ?<strong>then</strong>? <em>body2</em> <strong>elseif</strong> … ?<strong>else</strong>? ?<em>bodyN</em>?</tt></p></div>
+<div class="paragraph"><p>The <em>if</em> command evaluates <strong>expr1</strong> as an expression (in the same way
+that <em>expr</em> evaluates its argument). The value of the expression must
+be numeric; if it is non-zero then <strong>body1</strong> is executed by passing it to
+the Tcl interpreter.</p></div>
+<div class="paragraph"><p>Otherwise <strong>expr2</strong> is evaluated as an expression and if it is non-zero
+then <strong>body2</strong> is executed, and so on.</p></div>
+<div class="paragraph"><p>If none of the expressions evaluates to non-zero then <strong>bodyN</strong> is executed.</p></div>
+<div class="paragraph"><p>The <em>then</em> and <em>else</em> arguments are optional <em>noise words</em> to make the
+command easier to read.</p></div>
+<div class="paragraph"><p>There may be any number of <em>elseif</em> clauses, including zero. <strong>bodyN</strong>
+may also be omitted as long as <em>else</em> is omitted too.</p></div>
+<div class="paragraph"><p>The return value from the command is the result of the body script that
+was executed, or an empty string if none of the expressions was non-zero
+and there was no <strong>bodyN</strong>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_incr">incr</h3>
+<div class="paragraph"><p><tt><strong>incr</strong> <em>varName ?increment?</em></tt></p></div>
+<div class="paragraph"><p>Increment the value stored in the variable whose name is <strong>varName</strong>.
+The value of the variable must be integral.</p></div>
+<div class="paragraph"><p>If <strong>increment</strong> is supplied then its value (which must be an
+integer) is added to the value of variable <strong>varName</strong>; otherwise
+1 is added to <strong>varName</strong>.</p></div>
+<div class="paragraph"><p>The new value is stored as a decimal string in variable <strong>varName</strong>
+and also returned as result.</p></div>
+<div class="paragraph"><p>If the variable does not exist, the variable is implicitly created
+and set to <tt>0</tt> first.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_info">info</h3>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt><strong>info</strong> <em>option ?arg arg …?</em></tt>
+</dt>
+<dd>
+<p>
+Provide information about various internals to the Tcl interpreter.
+The legal <strong>option</strong>'s (which may be abbreviated) are:
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>info args</strong> <em>procname</em></tt>
+</dt>
+<dd>
+<p>
+ Returns a list containing the names of the arguments to procedure
+ <strong>procname</strong>, in order. <strong>Procname</strong> must be the name of a
+ Tcl command procedure.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>info body</strong> <em>procname</em></tt>
+</dt>
+<dd>
+<p>
+ Returns the body of procedure <strong>procname</strong>. <strong>Procname</strong> must be
+ the name of a Tcl command procedure.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>info commands</strong> ?<em>pattern</em>?</tt>
+</dt>
+<dd>
+<p>
+ If <strong>pattern</strong> isn’t specified, returns a list of names of all the
+ Tcl commands, including both the built-in commands written in C and
+ the command procedures defined using the <em>proc</em> command.
+ If <strong>pattern</strong> is specified, only those names matching <strong>pattern</strong>
+ are returned. Matching is determined using the same rules as for
+ <em>string match</em>.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>info complete</strong> <em>command</em></tt>
+</dt>
+<dd>
+<p>
+ Returns 1 if <strong>command</strong> is a complete Tcl command in the sense of
+ having no unclosed quotes, braces, brackets or array element names,
+ If the command doesn’t appear to be complete then 0 is returned.
+ This command is typically used in line-oriented input environments
+ to allow users to type in commands that span multiple lines; if the
+ command isn’t complete, the script can delay evaluating it until additional
+ lines have been typed to complete the command.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>info exists</strong> <em>varName</em></tt>
+</dt>
+<dd>
+<p>
+ Returns <em>1</em> if the variable named <strong>varName</strong> exists in the
+ current context (either as a global or local variable), returns <em>0</em>
+ otherwise.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>info frame</strong> ?<em>number</em>?</tt>
+</dt>
+<dd>
+<p>
+ If <strong>number</strong> is not specified, this command returns a number
+ which is the same result as <em>info level</em> - the current stack frame level.
+ If <strong>number</strong> is specified, then the result is a list consisting of the procedure,
+ filename and line number for the procedure call at level <strong>number</strong> on the stack.
+ If <strong>number</strong> is positive then it selects a particular stack level (1 refers
+ to the top-most active procedure, 2 to the procedure it called, and
+ so on); otherwise it gives a level relative to the current level
+ (0 refers to the current procedure, -1 to its caller, and so on).
+ The level has an identical meaning to <em>info level</em>.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>info globals</strong> ?<em>pattern</em>?</tt>
+</dt>
+<dd>
+<p>
+ If <strong>pattern</strong> isn’t specified, returns a list of all the names
+ of currently-defined global variables.
+ If <strong>pattern</strong> is specified, only those names matching <strong>pattern</strong>
+ are returned. Matching is determined using the same rules as for
+ <em>string match</em>.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>info hostname</strong></tt>
+</dt>
+<dd>
+<p>
+ An alias for <em>os.gethostname</em> for compatibility with Tcl 6.x
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>info level</strong> ?<em>number</em>?</tt>
+</dt>
+<dd>
+<p>
+ If <strong>number</strong> is not specified, this command returns a number
+ giving the stack level of the invoking procedure, or 0 if the
+ command is invoked at top-level. If <strong>number</strong> is specified,
+ then the result is a list consisting of the name and arguments for the
+ procedure call at level <strong>number</strong> on the stack. If <strong>number</strong>
+ is positive then it selects a particular stack level (1 refers
+ to the top-most active procedure, 2 to the procedure it called, and
+ so on); otherwise it gives a level relative to the current level
+ (0 refers to the current procedure, -1 to its caller, and so on).
+ See the <em>uplevel</em> command for more information on what stack
+ levels mean.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>info locals</strong> ?<em>pattern</em>?</tt>
+</dt>
+<dd>
+<p>
+ If <strong>pattern</strong> isn’t specified, returns a list of all the names
+ of currently-defined local variables, including arguments to the
+ current procedure, if any. Variables defined with the <em>global</em>
+ and <em>upvar</em> commands will not be returned. If <strong>pattern</strong> is
+ specified, only those names matching <strong>pattern</strong> are returned.
+ Matching is determined using the same rules as for <em>string match</em>.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>info nameofexecutable</strong></tt>
+</dt>
+<dd>
+<p>
+ Returns the name of the binary file from which the application
+ was invoked, either
+ as a path relative to the current directory or as a full
+ path. If the path can’t be determined, returns the empty
+ string.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>info procs</strong> ?<em>pattern</em>?</tt>
+</dt>
+<dd>
+<p>
+ If <strong>pattern</strong> isn’t specified, returns a list of all the
+ names of Tcl command procedures.
+ If <strong>pattern</strong> is specified, only those names matching <strong>pattern</strong>
+ are returned. Matching is determined using the same rules as for
+ <em>string match</em>.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>info references</strong></tt>
+</dt>
+<dd>
+<p>
+ Returns a list of all references which have not yet been garbage
+ collected.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>info returncodes</strong> ?<em>code</em>?</tt>
+</dt>
+<dd>
+<p>
+ Returns a list representing the mapping of standard return codes
+ to names. e.g. <tt>{0 ok 1 error 2 return …}</tt>. If a code is given,
+ instead returns the name for the given code.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>info script</strong></tt>
+</dt>
+<dd>
+<p>
+ If a Tcl script file is currently being evaluated (i.e. there is a
+ call to <em>Jim_EvalFile</em> active or there is an active invocation
+ of the <em>source</em> command), then this command returns the name
+ of the innermost file being processed. Otherwise the command returns an
+ empty string.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>info source</strong> <em>script</em></tt>
+</dt>
+<dd>
+<p>
+ Returns the original source location of the given script as a list of
+ <tt>{filename linenumber}</tt>. If the source location can’t be determined, the
+ list <tt>{{} 0}</tt> is returned.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>info stacktrace</strong></tt>
+</dt>
+<dd>
+<p>
+ After an error is caught with <em>catch</em>, returns the stack trace as a list
+ of <tt>{procedure filename line …}</tt>.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>info version</strong></tt>
+</dt>
+<dd>
+<p>
+ Returns the version number for this version of Jim in the form <strong>x.yy</strong>.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>info vars</strong> ?<em>pattern</em>?</tt>
+</dt>
+<dd>
+<p>
+ If <strong>pattern</strong> isn’t specified,
+ returns a list of all the names of currently-visible variables, including
+ both locals and currently-visible globals.
+ If <strong>pattern</strong> is specified, only those names matching <strong>pattern</strong>
+ are returned. Matching is determined using the same rules as for
+ <em>string match</em>.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_join">join</h3>
+<div class="paragraph"><p><tt><strong>join</strong> <em>list ?joinString?</em></tt></p></div>
+<div class="paragraph"><p>The <strong>list</strong> argument must be a valid Tcl list. This command returns the
+string formed by joining all of the elements of <strong>list</strong> together with
+<strong>joinString</strong> separating each adjacent pair of elements.</p></div>
+<div class="paragraph"><p>The <strong>joinString</strong> argument defaults to a space character.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_kill">kill</h3>
+<div class="paragraph"><p><tt><strong>kill</strong> ?<em>SIG</em>|<strong>-0</strong>? <em>pid</em></tt></p></div>
+<div class="paragraph"><p>Sends the given signal to the process identified by <strong>pid</strong>.</p></div>
+<div class="paragraph"><p>The signal may be specified by name or number in one of the following forms:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+<tt>TERM</tt>
+</p>
+</li>
+<li>
+<p>
+<tt>SIGTERM</tt>
+</p>
+</li>
+<li>
+<p>
+<tt>-TERM</tt>
+</p>
+</li>
+<li>
+<p>
+<tt>15</tt>
+</p>
+</li>
+<li>
+<p>
+<tt>-15</tt>
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>The signal name may be in either upper or lower case.</p></div>
+<div class="paragraph"><p>The special signal name <em>-0</em> simply checks that a signal <strong>could</strong> be sent.</p></div>
+<div class="paragraph"><p>If no signal is specified, SIGTERM is used.</p></div>
+<div class="paragraph"><p>An error is raised if the signal could not be delivered.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_lambda_2">lambda</h3>
+<div class="paragraph"><p><tt><strong>lambda</strong> <em>args ?statics? body</em></tt></p></div>
+<div class="paragraph"><p>The <em>lambda</em> command is identical to <em>proc</em>, except rather than
+creating a named procedure, it creates an anonymous procedure and returns
+the name of the procedure.</p></div>
+<div class="paragraph"><p>See <em>proc</em> and GARBAGE COLLECTION, REFERENCES, LAMBDA for more detail.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_lappend">lappend</h3>
+<div class="paragraph"><p><tt><strong>lappend</strong> <em>varName value ?value value …?</em></tt></p></div>
+<div class="paragraph"><p>Treat the variable given by <strong>varName</strong> as a list and append each of
+the <strong>value</strong> arguments to that list as a separate element, with spaces
+between elements.</p></div>
+<div class="paragraph"><p>If <strong>varName</strong> doesn’t exist, it is created as a list with elements given
+by the <strong>value</strong> arguments. <em>lappend</em> is similar to <em>append</em> except that
+each <strong>value</strong> is appended as a list element rather than raw text.</p></div>
+<div class="paragraph"><p>This command provides a relatively efficient way to build up large lists.
+For example, <em>lappend a $b</em> is much more efficient than</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a [concat $a [list $b]]</tt></pre>
+</div></div>
+<div class="paragraph"><p>when <em>$a</em> is long.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_lassign">lassign</h3>
+<div class="paragraph"><p><tt><strong>lassign</strong> <em>list varName ?varName? …</em></tt></p></div>
+<div class="paragraph"><p>This command treats the value <strong>list</strong> as a list and assigns successive elements from that list to
+the variables given by the <strong>varName</strong> arguments in order. If there are more variable names than
+list elements, the remaining variables are set to the empty string. If there are more list ele-
+ments than variables, a list of unassigned elements is returned.</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>jim> lassign {1 2 3} a b; puts a=$a,b=$b
+3
+a=1,b=2</tt></pre>
+</div></div>
+</div>
+<div class="sect2">
+<h3 id="_local">local</h3>
+<div class="paragraph"><p><tt><strong>local</strong> <em>args</em></tt></p></div>
+<div class="paragraph"><p>Executes it’s arguments as a command (per <em>eval</em>) and considers the return
+value to be a procedure name, which is marked as having local scope.
+This means that when the current procedure exits, the specified
+procedure is deleted. This can be useful with <em>lambda</em> or simply
+local procedures.</p></div>
+<div class="paragraph"><p>In this example, a local procedure is created. Note that the procedure
+continues to have global scope while it is active.</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>proc outer {} {
+ # proc ... returns "inner" which is marked local
+ local proc inner {} {
+ # will be deleted when 'outer' exits
+ }</tt></pre>
+</div></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt> inner
+ ...
+}</tt></pre>
+</div></div>
+<div class="paragraph"><p>In this example, the lambda is deleted at the end of the procedure rather
+than waiting until garbage collection.</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>proc outer {} {
+ set x [lambda inner {args} {
+ # will be deleted when 'outer' exits
+ }]
+ # Use 'function' here which simply returns $x
+ local function $x</tt></pre>
+</div></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt> $x ...
+ ...
+}</tt></pre>
+</div></div>
+</div>
+<div class="sect2">
+<h3 id="_lindex">lindex</h3>
+<div class="paragraph"><p><tt><strong>lindex</strong> <em>list index</em></tt></p></div>
+<div class="paragraph"><p>Treats <strong>list</strong> as a Tcl list and returns element <strong>index</strong> from it
+(0 refers to the first element of the list).
+See STRING AND LIST INDEX SPECIFICATIONS for all allowed forms for <strong>index</strong>.</p></div>
+<div class="paragraph"><p>In extracting the element, <strong>lindex</strong> observes the same rules concerning
+braces and quotes and backslashes as the Tcl command interpreter; however,
+variable substitution and command substitution do not occur.</p></div>
+<div class="paragraph"><p>If <strong>index</strong> is negative or greater than or equal to the number of elements
+in <strong>value</strong>, then an empty string is returned.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_linsert">linsert</h3>
+<div class="paragraph"><p><tt><strong>linsert</strong> <em>list index element ?element element …?</em></tt></p></div>
+<div class="paragraph"><p>This command produces a new list from <strong>list</strong> by inserting all
+of the <strong>element</strong> arguments just before the element <strong>index</strong>
+of <strong>list</strong>. Each <strong>element</strong> argument will become
+a separate element of the new list. If <strong>index</strong> is less than
+or equal to zero, then the new elements are inserted at the
+beginning of the list. If <strong>index</strong> is greater than or equal
+to the number of elements in the list, then the new elements are
+appended to the list.</p></div>
+<div class="paragraph"><p>See STRING AND LIST INDEX SPECIFICATIONS for all allowed forms for <strong>index</strong>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_list">list</h3>
+<div class="paragraph"><p><tt><strong>list</strong> <em>arg ?arg …?</em></tt></p></div>
+<div class="paragraph"><p>This command returns a list comprised of all the arguments, <strong>arg</strong>. Braces
+and backslashes get added as necessary, so that the <em>index</em> command
+may be used on the result to re-extract the original arguments, and also
+so that <em>eval</em> may be used to execute the resulting list, with
+<strong>arg1</strong> comprising the command’s name and the other args comprising
+its arguments. <em>List</em> produces slightly different results than
+<em>concat</em>: <em>concat</em> removes one level of grouping before forming
+the list, while <em>list</em> works directly from the original arguments.
+For example, the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>list a b {c d e} {f {g h}}</tt></pre>
+</div></div>
+<div class="paragraph"><p>will return</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>a b {c d e} {f {g h}}</tt></pre>
+</div></div>
+<div class="paragraph"><p>while <em>concat</em> with the same arguments will return</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>a b c d e f {g h}</tt></pre>
+</div></div>
+</div>
+<div class="sect2">
+<h3 id="_llength">llength</h3>
+<div class="paragraph"><p><tt><strong>llength</strong> <em>list</em></tt></p></div>
+<div class="paragraph"><p>Treats <strong>list</strong> as a list and returns a decimal string giving
+the number of elements in it.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_lset">lset</h3>
+<div class="paragraph"><p><tt><strong>lset</strong> <em>varName ?index ..? newValue</em></tt></p></div>
+<div class="paragraph"><p>Sets an element in a list.</p></div>
+<div class="paragraph"><p>The <em>lset</em> command accepts a parameter, <strong>varName</strong>, which it interprets
+as the name of a variable containing a Tcl list. It also accepts
+zero or more indices into the list. Finally, it accepts a new value
+for an element of varName. If no indices are presented, the command
+takes the form:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>lset varName newValue</tt></pre>
+</div></div>
+<div class="paragraph"><p>In this case, newValue replaces the old value of the variable
+varName.</p></div>
+<div class="paragraph"><p>When presented with a single index, the <em>lset</em> command
+treats the content of the varName variable as a Tcl list. It addresses
+the index’th element in it (0 refers to the first element of the
+list). When interpreting the list, <em>lset</em> observes the same rules
+concerning braces and quotes and backslashes as the Tcl command
+interpreter; however, variable substitution and command substitution
+do not occur. The command constructs a new list in which the
+designated element is replaced with newValue. This new list is
+stored in the variable varName, and is also the return value from
+the <em>lset</em> command.</p></div>
+<div class="paragraph"><p>If index is negative or greater than or equal to the number of
+elements in $varName, then an error occurs.</p></div>
+<div class="paragraph"><p>See STRING AND LIST INDEX SPECIFICATIONS for all allowed forms for <strong>index</strong>.</p></div>
+<div class="paragraph"><p>If additional index arguments are supplied, then each argument is
+used in turn to address an element within a sublist designated by
+the previous indexing operation, allowing the script to alter
+elements in sublists. The command,</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>lset a 1 2 newValue</tt></pre>
+</div></div>
+<div class="paragraph"><p>replaces element 2 of sublist 1 with <strong>newValue</strong>.</p></div>
+<div class="paragraph"><p>The integer appearing in each index argument must be greater than
+or equal to zero. The integer appearing in each index argument must
+be strictly less than the length of the corresponding list. In other
+words, the <em>lset</em> command cannot change the size of a list. If an
+index is outside the permitted range, an error is reported.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_lmap">lmap</h3>
+<div class="paragraph"><p><tt><strong>lmap</strong> <em>varName list body</em></tt></p></div>
+<div class="paragraph"><p><tt><strong>lmap</strong> <em>varList list ?varList2 list2 …? body</em></tt></p></div>
+<div class="paragraph"><p><em>lmap</em> is a "collecting <em>foreach</em>" which returns a list of its results.</p></div>
+<div class="paragraph"><p>For example:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>jim> lmap i {1 2 3 4 5} {expr $i*$i}
+1 4 9 16 25
+jim> lmap a {1 2 3} b {A B C} {list $a $b}
+{1 A} {2 B} {3 C}</tt></pre>
+</div></div>
+<div class="paragraph"><p>If the body invokes <em>continue</em>, no value is added for this iteration.
+If the body invokes <em>break</em>, the loop ends and no more values are added.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_lrange">lrange</h3>
+<div class="paragraph"><p><tt><strong>lrange</strong> <em>list first last</em></tt></p></div>
+<div class="paragraph"><p><strong>List</strong> must be a valid Tcl list. This command will return a new
+list consisting of elements <strong>first</strong> through <strong>last</strong>, inclusive.</p></div>
+<div class="paragraph"><p>See STRING AND LIST INDEX SPECIFICATIONS for all allowed forms for <strong>first</strong> and <strong>last</strong>.</p></div>
+<div class="paragraph"><p>If <strong>last</strong> is greater than or equal to the number of elements
+in the list, then it is treated as if it were <em>end</em>.</p></div>
+<div class="paragraph"><p>If <strong>first</strong> is greater than <strong>last</strong> then an empty string
+is returned.</p></div>
+<div class="paragraph"><p>Note: <em>lrange <strong>list first first</strong></em> does not always produce the
+same result as <em>lindex <strong>list first</strong></em> (although it often does
+for simple fields that aren’t enclosed in braces); it does, however,
+produce exactly the same results as <em>list [lindex <strong>list first</strong>]</em></p></div>
+</div>
+<div class="sect2">
+<h3 id="_lreplace">lreplace</h3>
+<div class="paragraph"><p><tt><strong>lreplace</strong> <em>list first last ?element element …?</em></tt></p></div>
+<div class="paragraph"><p>Returns a new list formed by replacing one or more elements of
+<strong>list</strong> with the <strong>element</strong> arguments.</p></div>
+<div class="paragraph"><p><strong>First</strong> gives the index in <strong>list</strong> of the first element
+to be replaced.</p></div>
+<div class="paragraph"><p>If <strong>first</strong> is less than zero then it refers to the first
+element of <strong>list</strong>; the element indicated by <strong>first</strong>
+must exist in the list.</p></div>
+<div class="paragraph"><p><strong>Last</strong> gives the index in <strong>list</strong> of the last element
+to be replaced; it must be greater than or equal to <strong>first</strong>.</p></div>
+<div class="paragraph"><p>See STRING AND LIST INDEX SPECIFICATIONS for all allowed forms for <strong>first</strong> and <strong>last</strong>.</p></div>
+<div class="paragraph"><p>The <strong>element</strong> arguments specify zero or more new arguments to
+be added to the list in place of those that were deleted.</p></div>
+<div class="paragraph"><p>Each <strong>element</strong> argument will become a separate element of
+the list.</p></div>
+<div class="paragraph"><p>If no <strong>element</strong> arguments are specified, then the elements
+between <strong>first</strong> and <strong>last</strong> are simply deleted.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_lrepeat">lrepeat</h3>
+<div class="paragraph"><p><tt><strong>lrepeat</strong> <em>number element1 ?element2 …?</em></tt></p></div>
+<div class="paragraph"><p>Build a list by repeating elements <strong>number</strong> times (which must be
+a positive integer).</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>jim> lrepeat 3 a b
+a b a b a b</tt></pre>
+</div></div>
+</div>
+<div class="sect2">
+<h3 id="_lreverse">lreverse</h3>
+<div class="paragraph"><p><tt><strong>lreverse</strong> <em>list</em></tt></p></div>
+<div class="paragraph"><p>Returns the list in reverse order.</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>jim> lreverse {1 2 3}
+3 2 1</tt></pre>
+</div></div>
+</div>
+<div class="sect2">
+<h3 id="_lsearch">lsearch</h3>
+<div class="paragraph"><p><tt><strong>lsearch</strong> <em>?options? list pattern</em></tt></p></div>
+<div class="paragraph"><p>This command searches the elements <strong>list</strong> to see if one of them matches <strong>pattern</strong>. If so, the
+command returns the index of the first matching element (unless the options -all, -inline or -bool are
+specified.) If not, the command returns -1. The option arguments indicates how the elements of
+the list are to be matched against pattern and must have one of the values below:</p></div>
+<div class="paragraph"><p><strong>Note</strong> that this command is different from Tcl in that default match type is <em>-exact</em> rather than <em>-glob</em>.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt><em>-exact</em></tt>
+</dt>
+<dd>
+<p>
+ <strong>pattern</strong> is a literal string that is compared for exact equality against each list element.
+ This is the default.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><em>-glob</em></tt>
+</dt>
+<dd>
+<p>
+ <strong>pattern</strong> is a glob-style pattern which is matched against each list element using the same
+ rules as the string match command.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><em>-regexp</em></tt>
+</dt>
+<dd>
+<p>
+ <strong>pattern</strong> is treated as a regular expression and matched against each list element using
+ the rules described by <em>regexp</em>.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><em>-all</em></tt>
+</dt>
+<dd>
+<p>
+ Changes the result to be the list of all matching indices (or all matching values if
+ <em>-inline</em> is specified as well). If indices are returned, the indices will be in numeric
+ order. If values are returned, the order of the values will be the order of those values
+ within the input list.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><em>-inline</em></tt>
+</dt>
+<dd>
+<p>
+ The matching value is returned instead of its index (or an empty string if no value
+ matches). If <em>-all</em> is also specified, then the result of the command is the list of all
+ values that matched. The <em>-inline</em> and <em>-bool</em> options are mutually exclusive.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><em>-bool</em></tt>
+</dt>
+<dd>
+<p>
+ Changes the result to <em>1</em> if a match was found, or <em>0</em> otherwise. If <em>-all</em> is also specified,
+ the result will be a list of <em>0</em> and <em>1</em> for each element of the list depending upon whether
+ the corresponding element matches. The <em>-inline</em> and <em>-bool</em> options are mutually exclusive.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><em>-not</em></tt>
+</dt>
+<dd>
+<p>
+ This negates the sense of the match, returning the index (or value
+ if <em>-inline</em> is specified) of the first non-matching value in the
+ list. If <em>-bool</em> is also specified, the <em>0</em> will be returned if a
+ match is found, or <em>1</em> otherwise. If <em>-all</em> is also specified,
+ non-matches will be returned rather than matches.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><em>-nocase</em></tt>
+</dt>
+<dd>
+<p>
+ Causes comparisons to be handled in a case-insensitive manner.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_lsort">lsort</h3>
+<div class="paragraph"><p><tt><strong>lsort</strong> ?<strong>-integer</strong>|<strong>-command</strong> <em>cmdname</em>? ?<strong>-decreasing</strong>|<strong>-increasing</strong>? <em>list</em></tt></p></div>
+<div class="paragraph"><p>Sort the elements of <strong>list</strong>, returning a new list in sorted order.
+By default, ASCII sorting is used, with the result in increasing order.</p></div>
+<div class="paragraph"><p>If <strong>-integer</strong> is specified, numeric sorting is used.</p></div>
+<div class="paragraph"><p>If <strong>-command cmdname</strong> is specified, <strong>cmdname</strong> is treated as a
+command name. For each comparison, <strong>cmdname $value1 $value2</strong> is called
+which should return <em>-1</em> if <strong>$value1</strong> is less than <strong>$value2</strong>, <em>0</em> if
+they are equal, or <em>1</em> otherwise.</p></div>
+<div class="paragraph"><p>If <strong>-decreasing</strong> is specified, the resulting list is in the opposite
+order to what it would be otherwise. <strong>-increasing</strong> is the default.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_open">open</h3>
+<div class="paragraph"><p><tt><strong>open</strong> <em>fileName ?access?</em></tt></p></div>
+<div class="paragraph"><p><tt><strong>open</strong> <em>|command-pipeline ?access?</em></tt></p></div>
+<div class="paragraph"><p>Opens a file and returns an identifier
+that may be used in future invocations
+of commands like <em>read</em>, <em>puts</em>, and <em>close</em>.
+<strong>fileName</strong> gives the name of the file to open.</p></div>
+<div class="paragraph"><p>The <strong>access</strong> argument indicates the way in which the file is to be accessed.
+It may have any of the following values:</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt>r</tt>
+</dt>
+<dd>
+<p>
+ Open the file for reading only; the file must already exist.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>r</tt>+
+</dt>
+<dd>
+<p>
+ Open the file for both reading and writing; the file must
+ already exist.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>w</tt>
+</dt>
+<dd>
+<p>
+ Open the file for writing only. Truncate it if it exists. If it doesn’t
+ exist, create a new file.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>w</tt>+
+</dt>
+<dd>
+<p>
+ Open the file for reading and writing. Truncate it if it exists.
+ If it doesn’t exist, create a new file.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>a</tt>
+</dt>
+<dd>
+<p>
+ Open the file for writing only. The file must already exist, and the file
+ is positioned so that new data is appended to the file.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>a</tt>+
+</dt>
+<dd>
+<p>
+ Open the file for reading and writing. If the file doesn’t
+ exist, create a new empty file. Set the initial access position
+ to the end of the file.
+</p>
+</dd>
+</dl></div>
+<div class="paragraph"><p><strong>Access</strong> defaults to <em>r</em>.</p></div>
+<div class="paragraph"><p>If a file is opened for both reading and writing, then <em>seek</em>
+must be invoked between a read and a write, or vice versa.</p></div>
+<div class="paragraph"><p>If the first character of <strong>fileName</strong> is "|" then the remaining
+characters of <strong>fileName</strong> are treated as a list of arguments that
+describe a command pipeline to invoke, in the same style as the
+arguments for exec. In this case, the channel identifier returned
+by open may be used to write to the command’s input pipe or read
+from its output pipe, depending on the value of <strong>access</strong>. If write-only
+access is used (e.g. <strong>access</strong> is <em>w</em>), then standard output for the
+pipeline is directed to the current standard output unless overridden
+by the command. If read-only access is used (e.g. <strong>access</strong> is r),
+standard input for the pipeline is taken from the current standard
+input unless overridden by the command.</p></div>
+<div class="paragraph"><p>The <em>pid</em> command may be used to return the process ids of the commands
+forming the command pipeline.</p></div>
+<div class="paragraph"><p>See also <em>socket</em>, <em>pid</em>, <em>exec</em></p></div>
+</div>
+<div class="sect2">
+<h3 id="_package">package</h3>
+<div class="paragraph"><p><tt><strong>package provide</strong> <em>name ?version?</em></tt></p></div>
+<div class="paragraph"><p>Indicates that the current script provides the package named <strong>name</strong>.
+If no version is specified, <em>1.0</em> is used.</p></div>
+<div class="paragraph"><p>Any script which provides a package may include this statement
+as the first statement, although it is not required.</p></div>
+<div class="paragraph"><p><tt><strong>package require</strong> <em>name ?version?</em>*</tt></p></div>
+<div class="paragraph"><p>Searches for the package with the given <strong>name</strong> by examining each path
+in <em>$::auto_path</em> and trying to load <em>$path/$name.tcl</em>.</p></div>
+<div class="paragraph"><p>If either file exists, it is loaded with <em>source</em>.</p></div>
+<div class="paragraph"><p>Typically <em>$::auto_path</em> contains the paths <em>.</em> and <em>/lib/jim</em>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_pid">pid</h3>
+<div class="paragraph"><p><tt><strong>pid</strong></tt></p></div>
+<div class="paragraph"><p><tt><strong>pid</strong> <em>fileId</em></tt></p></div>
+<div class="paragraph"><p>The first form returns the process identifier of the current process.</p></div>
+<div class="paragraph"><p>The second form accepts a handle returned by <em>open</em> and returns a list
+of the process ids forming the pipeline in the same form as <em>exec … &</em>.
+If <em>fileId</em> represents a regular file handle rather than a command pipeline,
+the empty string is returned instead.</p></div>
+<div class="paragraph"><p>See also <em>open</em>, <em>exec</em></p></div>
+</div>
+<div class="sect2">
+<h3 id="_proc">proc</h3>
+<div class="paragraph"><p><tt><strong>proc</strong> <em>name args ?statics? body</em></tt></p></div>
+<div class="paragraph"><p>The <em>proc</em> command creates a new Tcl command procedure, <strong>name</strong>.
+When the new command is invoked, the contents of <strong>body</strong> will be executed.
+Tcl interpreter. <strong>args</strong> specifies the formal arguments to the procedure.
+If specified, <strong>static</strong>, declares static variables which are bound to the
+procedure.</p></div>
+<div class="paragraph"><p>See PROCEDURES for detailed information about Tcl procedures.</p></div>
+<div class="paragraph"><p>The <em>proc</em> command returns <strong>name</strong> (which is useful with <em>local</em>).</p></div>
+<div class="paragraph"><p>When a procedure is invoked, the procedure’s return value is the
+value specified in a <em>return</em> command. If the procedure doesn’t
+execute an explicit <em>return</em>, then its return value is the value
+of the last command executed in the procedure’s body.</p></div>
+<div class="paragraph"><p>If an error occurs while executing the procedure body, then the
+procedure-as-a-whole will return that same error.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_puts">puts</h3>
+<div class="paragraph"><p><tt><strong>puts</strong> ?<strong>-nonewline</strong>? <em>?fileId? string</em></tt></p></div>
+<div class="paragraph"><p><tt><em>fileId</em> <strong>puts</strong> ?<strong>-nonewline</strong>? <em>string</em></tt></p></div>
+<div class="paragraph"><p>Writes the characters given by <strong>string</strong> to the file given
+by <strong>fileId</strong>. <strong>fileId</strong> must have been the return
+value from a previous call to <em>open</em>, or it may be
+<em>stdout</em> or <em>stderr</em> to refer to one of the standard I/O
+channels; it must refer to a file that was opened for
+writing.</p></div>
+<div class="paragraph"><p>In the first form, if no <strong>fileId</strong> is specified then it defaults to <em>stdout</em>.
+<em>puts</em> normally outputs a newline character after <strong>string</strong>,
+but this feature may be suppressed by specifying the <em>-nonewline</em>
+switch.</p></div>
+<div class="paragraph"><p>Output to files is buffered internally by Tcl; the <em>flush</em>
+command may be used to force buffered characters to be output.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_pwd">pwd</h3>
+<div class="paragraph"><p><tt><strong>pwd</strong></tt></p></div>
+<div class="paragraph"><p>Returns the path name of the current working directory.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_rand">rand</h3>
+<div class="paragraph"><p><tt><strong>rand</strong> <em>?min? ?max?</em></tt></p></div>
+<div class="paragraph"><p>Returns a random integer between <strong>min</strong> (defaults to 0) and <strong>max</strong>
+(defaults to the maximum integer).</p></div>
+<div class="paragraph"><p>If only one argument is given, it is interpreted as <strong>max</strong>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_range">range</h3>
+<div class="paragraph"><p><tt><strong>range</strong> <em>?start? end ?step?</em></tt></p></div>
+<div class="paragraph"><p>Returns a list of integers starting at <strong>start</strong> (defaults to 0)
+and ranging up to but not including <strong>end</strong> in steps of <strong>step</strong> defaults to 1).</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>jim> range 5
+0 1 2 3 4
+jim> range 2 5
+2 3 4
+jim> range 2 10 4
+2 6
+jim> range 7 4 -2
+7 5</tt></pre>
+</div></div>
+</div>
+<div class="sect2">
+<h3 id="_read">read</h3>
+<div class="paragraph"><p><tt><strong>read</strong> ?<strong>-nonewline</strong>? <em>fileId</em></tt></p></div>
+<div class="paragraph"><p><tt><em>fileId</em> <strong>read</strong> ?<strong>-nonewline</strong>?</tt></p></div>
+<div class="paragraph"><p><tt><strong>read</strong> <em>fileId numBytes</em></tt></p></div>
+<div class="paragraph"><p><tt><em>fileId</em> <strong>read</strong> <em>numBytes</em></tt></p></div>
+<div class="paragraph"><p>In the first form, all of the remaining bytes are read from the file
+given by <strong>fileId</strong>; they are returned as the result of the command.
+If the <em>-nonewline</em> switch is specified then the last
+character of the file is discarded if it is a newline.</p></div>
+<div class="paragraph"><p>In the second form, the extra argument specifies how many bytes to read;
+exactly this many bytes will be read and returned, unless there are fewer than
+<strong>numBytes</strong> bytes left in the file; in this case, all the remaining
+bytes are returned.</p></div>
+<div class="paragraph"><p><strong>fileId</strong> must be <em>stdin</em> or the return value from a previous call
+to <em>open</em>; it must refer to a file that was opened for reading.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_regexp">regexp</h3>
+<div class="paragraph"><p><tt><strong>regexp ?-nocase? ?-line? ?-indices? ?-start</strong> <em>offset</em>? <strong>?-all? ?-inline? ?--?</strong> <em>exp string ?matchVar? ?subMatchVar subMatchVar …?</em></tt></p></div>
+<div class="paragraph"><p>Determines whether the regular expression <strong>exp</strong> matches part or
+all of <strong>string</strong> and returns 1 if it does, 0 if it doesn’t.</p></div>
+<div class="paragraph"><p>See REGULAR EXPRESSIONS above for complete information on the
+syntax of <strong>exp</strong> and how it is matched against <strong>string</strong>.</p></div>
+<div class="paragraph"><p>If additional arguments are specified after <strong>string</strong> then they
+are treated as the names of variables to use to return
+information about which part(s) of <strong>string</strong> matched <strong>exp</strong>.
+<strong>matchVar</strong> will be set to the range of <strong>string</strong> that
+matched all of <strong>exp</strong>. The first <strong>subMatchVar</strong> will contain
+the characters in <strong>string</strong> that matched the leftmost parenthesized
+subexpression within <strong>exp</strong>, the next <strong>subMatchVar</strong> will
+contain the characters that matched the next parenthesized
+subexpression to the right in <strong>exp</strong>, and so on.</p></div>
+<div class="paragraph"><p>Normally, <strong>matchVar</strong> and the each <strong>subMatchVar</strong> are set to hold the
+matching characters from <em>string</em>, however see <em>-indices</em> and
+<em>-inline</em> below.</p></div>
+<div class="paragraph"><p>If there are more values for <strong>subMatchVar</strong> than parenthesized subexpressions
+within <strong>exp</strong>, or if a particular subexpression in <strong>exp</strong> doesn’t
+match the string (e.g. because it was in a portion of the expression
+that wasn’t matched), then the corresponding <strong>subMatchVar</strong> will be
+set to <em>"-1 -1"</em> if <em>-indices</em> has been specified or to an empty
+string otherwise.</p></div>
+<div class="paragraph"><p>The following switches modify the behaviour of <strong>regexp</strong></p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt><strong>-nocase</strong></tt>
+</dt>
+<dd>
+<p>
+ Causes upper-case and lower-case characters to be treated as
+ identical during the matching process.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>-line</strong></tt>
+</dt>
+<dd>
+<p>
+ Use newline-sensitive matching. By default, newline
+ is a completely ordinary character with no special meaning in
+ either REs or strings. With this flag, <em>[<sup></em> bracket expressions
+ and <em>.</em> never match newline, a <em></sup></em> anchor matches the null
+ string after any newline in the string in addition to its normal
+ function, and the <em>$</em> anchor matches the null string before any
+ newline in the string in addition to its normal function.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>-indices</strong></tt>
+</dt>
+<dd>
+<p>
+ Changes what is stored in the subMatchVars. Instead of
+ storing the matching characters from string, each variable
+ will contain a list of two decimal strings giving the indices
+ in string of the first and last characters in the matching
+ range of characters.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>-start</strong> <em>offset</em></tt>
+</dt>
+<dd>
+<p>
+ Specifies a character index offset into the string at which to start
+ matching the regular expression. If <em>-indices</em> is
+ specified, the indices will be indexed starting from the
+ absolute beginning of the input string. <strong>offset</strong> will be
+ constrained to the bounds of the input string.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>-all</strong></tt>
+</dt>
+<dd>
+<p>
+ Causes the regular expression to be matched as many times as possible
+ in the string, returning the total number of matches found. If this
+ is specified with match variables, they will contain information
+ for the last match only.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>-inline</strong></tt>
+</dt>
+<dd>
+<p>
+ Causes the command to return, as a list, the data that would otherwise
+ be placed in match variables. When using <em>-inline</em>, match variables
+ may not be specified. If used with <em>-all</em>, the list will be concatenated
+ at each iteration, such that a flat list is always returned. For
+ each match iteration, the command will append the overall match
+ data, plus one element for each subexpression in the regular
+ expression.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>--</strong></tt>
+</dt>
+<dd>
+<p>
+ Marks the end of switches. The argument following this one will be
+ treated as <strong>exp</strong> even if it starts with a <tt>-</tt>.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_regsub">regsub</h3>
+<div class="paragraph"><p><tt><strong>regsub ?-nocase? ?-all? ?-line? ?-start</strong> <em>offset</em>? ?<strong>--</strong>? <em>exp string subSpec ?varName?</em></tt></p></div>
+<div class="paragraph"><p>This command matches the regular expression <strong>exp</strong> against
+<strong>string</strong> using the rules described in REGULAR EXPRESSIONS
+above.</p></div>
+<div class="paragraph"><p>If <strong>varName</strong> is specified, the commands stores <strong>string</strong> to <strong>varName</strong>
+with the susbstitutions detailed below, and returns the number of
+substitutions made (normally 1 unless <em>-all</em> is specified).
+This is 0 if there were no matches.</p></div>
+<div class="paragraph"><p>If <strong>varName</strong> is not specified, the substituted string will be returned
+instead.</p></div>
+<div class="paragraph"><p>When copying <strong>string</strong>, the portion of <strong>string</strong> that
+matched <strong>exp</strong> is replaced with <strong>subSpec</strong>.
+If <strong>subSpec</strong> contains a <em>&</em> or <em>\0</em>, then it is replaced
+in the substitution with the portion of <strong>string</strong> that
+matched <strong>exp</strong>.</p></div>
+<div class="paragraph"><p>If <strong>subSpec</strong> contains a <em>\<strong>n</strong></em>, where <strong>n</strong> is a digit
+between 1 and 9, then it is replaced in the substitution with
+the portion of <strong>string</strong> that matched the <strong>n</strong>-th
+parenthesized subexpression of <strong>exp</strong>.
+Additional backslashes may be used in <strong>subSpec</strong> to prevent special
+interpretation of <em>&</em> or <em>\0</em> or <em>\<strong>n</strong></em> or
+backslash.</p></div>
+<div class="paragraph"><p>The use of backslashes in <strong>subSpec</strong> tends to interact badly
+with the Tcl parser’s use of backslashes, so it’s generally
+safest to enclose <strong>subSpec</strong> in braces if it includes
+backslashes.</p></div>
+<div class="paragraph"><p>The following switches modify the behaviour of <strong>regsub</strong></p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt><strong>-nocase</strong></tt>
+</dt>
+<dd>
+<p>
+ Upper-case characters in <strong>string</strong> are converted to lower-case
+ before matching against <strong>exp</strong>; however, substitutions
+ specified by <strong>subSpec</strong> use the original unconverted form
+ of <strong>string</strong>.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>-all</strong></tt>
+</dt>
+<dd>
+<p>
+ All ranges in <strong>string</strong> that match <strong>exp</strong> are found and substitution
+ is performed for each of these ranges, rather than only the
+ first. The <em>&</em> and <em>\<strong>n</strong></em> sequences are handled for
+ each substitution using the information from the corresponding
+ match.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>-line</strong></tt>
+</dt>
+<dd>
+<p>
+ Use newline-sensitive matching. By default, newline
+ is a completely ordinary character with no special meaning in
+ either REs or strings. With this flag, <em>[<sup></em> bracket expressions
+ and <em>.</em> never match newline, a <em></sup></em> anchor matches the null
+ string after any newline in the string in addition to its normal
+ function, and the <em>$</em> anchor matches the null string before any
+ newline in the string in addition to its normal function.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>-start</strong> <em>offset</em></tt>
+</dt>
+<dd>
+<p>
+ Specifies a character index offset into the string at which to
+ start matching the regular expression. <strong>offset</strong> will be
+ constrained to the bounds of the input string.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>--</strong></tt>
+</dt>
+<dd>
+<p>
+ Marks the end of switches. The argument following this one will be
+ treated as <strong>exp</strong> even if it starts with a <tt>-</tt>.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_ref">ref</h3>
+<div class="paragraph"><p><tt><strong>ref</strong> <em>string tag ?finalizer?</em></tt></p></div>
+<div class="paragraph"><p>Create a new reference containing <strong>string</strong> of type <strong>tag</strong>.
+If <strong>finalizer</strong> is specified, it is a command which will be invoked
+when the a garbage collection cycle runs and this reference is
+no longer accessible.</p></div>
+<div class="paragraph"><p>The finalizer is invoked as:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>+finalizer 'reference string'+</tt></pre>
+</div></div>
+<div class="paragraph"><p>See GARBAGE COLLECTION, REFERENCES, LAMBDA for more detail.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_rename">rename</h3>
+<div class="paragraph"><p><tt><strong>rename</strong> <em>oldName newName</em></tt></p></div>
+<div class="paragraph"><p>Rename the command that used to be called <strong>oldName</strong> so that it
+is now called <strong>newName</strong>. If <strong>newName</strong> is an empty string
+(e.g. {}) then <strong>oldName</strong> is deleted. The <em>rename</em> command
+returns an empty string as result.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_return">return</h3>
+<div class="paragraph"><p><tt><strong>return</strong> ?<strong>-code</strong> <em>code</em>? ?<strong>-errorinfo</strong> <em>stacktrace</em>? ?<strong>-errorcode</strong> <em>errorcode</em>? ?<strong>-level</strong> <em>n</em>? ?<em>value</em>?</tt></p></div>
+<div class="paragraph"><p>Return immediately from the current procedure (or top-level command
+or <em>source</em> command), with <strong>value</strong> as the return value. If <strong>value</strong>
+is not specified, an empty string will be returned as result.</p></div>
+<div class="paragraph"><p>If <strong>-code</strong> is specified (as either a number or ok, error, break,
+continue, signal, return or exit), this code will be used instead
+of <tt>JIM_OK</tt>. This is generally useful when implementing flow of control
+commands.</p></div>
+<div class="paragraph"><p>If <strong>-level</strong> is specified and greater than 1, it has the effect of delaying
+the new return code from <strong>-code</strong>. This is useful when rethrowing an error
+from <em>catch</em>. See the implementation of try/catch in tclcompat.tcl for
+an example of how this is done.</p></div>
+<div class="paragraph"><p>Note: The following options are only used when <strong>-code</strong> is JIM_ERR.</p></div>
+<div class="paragraph"><p>If <strong>-errorinfo</strong> is specified (as returned from <em>info stacktrace</em>)
+it is used to initialize the stacktrace.</p></div>
+<div class="paragraph"><p>If <strong>-errorcode</strong> is specified, it is used to set the global variable $::errorCode.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_scan">scan</h3>
+<div class="paragraph"><p><tt><strong>scan</strong> <em>string format varName1 ?varName2 …?</em></tt></p></div>
+<div class="paragraph"><p>This command parses fields from an input string in the same fashion
+as the C <em>sscanf</em> procedure. <strong>String</strong> gives the input to be parsed
+and <strong>format</strong> indicates how to parse it, using <em>%</em> fields as in
+<em>sscanf</em>. All of the <em>sscanf</em> options are valid; see the <em>sscanf</em>
+man page for details. Each <strong>varName</strong> gives the name of a variable;
+when a field is scanned from <strong>string</strong>, the result is converted back
+into a string and assigned to the corresponding <strong>varName</strong>. The
+only unusual conversion is for <em>%c</em>. For <em>%c</em> conversions a single
+character value is converted to a decimal string, which is then
+assigned to the corresponding <strong>varName</strong>; no field width may be
+specified for this conversion.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_seek">seek</h3>
+<div class="paragraph"><p><tt><strong>seek</strong> <em>fileId offset ?origin?</em></tt></p></div>
+<div class="paragraph"><p><tt><em>fileId</em> <strong>seek</strong> <em>offset ?origin?</em></tt></p></div>
+<div class="paragraph"><p>Change the current access position for <strong>fileId</strong>.
+The <strong>offset</strong> and <strong>origin</strong> arguments specify the position at
+which the next read or write will occur for <strong>fileId</strong>.
+<strong>offset</strong> must be a number (which may be negative) and <strong>origin</strong>
+must be one of the following:</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt><strong>start</strong></tt>
+</dt>
+<dd>
+<p>
+ The new access position will be <strong>offset</strong> bytes from the start
+ of the file.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>current</strong></tt>
+</dt>
+<dd>
+<p>
+ The new access position will be <strong>offset</strong> bytes from the current
+ access position; a negative <strong>offset</strong> moves the access position
+ backwards in the file.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>end</strong></tt>
+</dt>
+<dd>
+<p>
+ The new access position will be <strong>offset</strong> bytes from the end of
+ the file. A negative <strong>offset</strong> places the access position before
+ the end-of-file, and a positive <strong>offset</strong> places the access position
+ after the end-of-file.
+</p>
+</dd>
+</dl></div>
+<div class="paragraph"><p>The <strong>origin</strong> argument defaults to <em>start</em>.</p></div>
+<div class="paragraph"><p><strong>fileId</strong> must have been the return value from a previous call to
+<em>open</em>, or it may be <em>stdin</em>, <em>stdout</em>, or <em>stderr</em> to refer to one
+of the standard I/O channels.</p></div>
+<div class="paragraph"><p>This command returns an empty string.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_set">set</h3>
+<div class="paragraph"><p><tt><strong>set</strong> <em>varName ?value?</em></tt></p></div>
+<div class="paragraph"><p>Returns the value of variable <strong>varName</strong>.</p></div>
+<div class="paragraph"><p>If <strong>value</strong> is specified, then set the value of <strong>varName</strong> to <strong>value</strong>,
+creating a new variable if one doesn’t already exist, and return
+its value.</p></div>
+<div class="paragraph"><p>If <strong>varName</strong> contains an open parenthesis and ends with a
+close parenthesis, then it refers to an array element: the characters
+before the open parenthesis are the name of the array, and the characters
+between the parentheses are the index within the array.
+Otherwise <strong>varName</strong> refers to a scalar variable.</p></div>
+<div class="paragraph"><p>If no procedure is active, then <strong>varName</strong> refers to a global
+variable.</p></div>
+<div class="paragraph"><p>If a procedure is active, then <strong>varName</strong> refers to a parameter
+or local variable of the procedure, unless the <strong>global</strong> command
+has been invoked to declare <strong>varName</strong> to be global.</p></div>
+<div class="paragraph"><p>The <em>::</em> prefix may also be used to explicitly reference a variable
+in the global scope.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_setref">setref</h3>
+<div class="paragraph"><p><tt><strong>setref</strong> <em>reference string</em></tt></p></div>
+<div class="paragraph"><p>Store a new string in <strong>reference</strong>, replacing the existing string.
+The reference must be a valid reference create with the <em>ref</em>
+command.</p></div>
+<div class="paragraph"><p>See GARBAGE COLLECTION, REFERENCES, LAMBDA for more detail.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_signal">signal</h3>
+<div class="paragraph"><p>Command for signal handling.</p></div>
+<div class="paragraph"><p>See <em>kill</em> for the different forms which may be used to specify signals.</p></div>
+<div class="paragraph"><p>Commands which return a list of signal names do so using the canonical form:
+"<tt>SIGINT SIGTERM</tt>".</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt><strong>signal handle</strong> ?<em>signals …</em>?</tt>
+</dt>
+<dd>
+<p>
+ If no signals are given, returns a list of all signals which are currently
+ being handled.
+ If signals are specified, these are added to the list of signals currently
+ being handled.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>signal ignore</strong> ?<em>signals …</em>?</tt>
+</dt>
+<dd>
+<p>
+ If no signals are given, returns a lists all signals which are currently
+ being ignored.
+ If signals are specified, these are added to the list of signals
+ currently being ignored. These signals are still delivered, but
+ are not considered by <em>catch -signal</em> or <em>try -signal</em>. Use
+ <em>signal check</em> to determine which signals have occurred but
+ been ignored.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>signal default</strong> ?<em>signals …</em>?</tt>
+</dt>
+<dd>
+<p>
+ If no signals are given, returns a lists all signals which are currently have
+ the default behaviour.
+ If signals are specified, these are added to the list of signals which have
+ the default behaviour.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>signal check ?-clear?</strong> ?<em>signals …</em>?</tt>
+</dt>
+<dd>
+<p>
+ Returns a list of signals which have been delivered to the process
+ but are <em>ignored</em>. If signals are specified, only that set of signals will
+ be checked, otherwise all signals will be checked.
+ If <em>-clear</em> is specified, any signals returned are removed and will not be
+ returned by subsequent calls to <em>signal check</em> unless delivered again.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>signal throw</strong> ?<em>signal</em>?</tt>
+</dt>
+<dd>
+<p>
+ Raises the given signal, which defaults to <tt>SIGINT</tt> if not specified.
+ The behaviour is identical to:
+</p>
+<div class="literalblock">
+<div class="content">
+<pre><tt>kill signal [pid]</tt></pre>
+</div></div>
+</dd>
+</dl></div>
+<div class="paragraph"><p>Note that <em>signal handle</em> and <em>signal ignore</em> represent two forms of signal
+handling. <em>signal handle</em> is used in conjunction with <em>catch -signal</em> or <em>try -signal</em>
+to immediately abort execution when the signal is delivered. Alternatively, <em>signal ignore</em>
+is used in conjunction with <em>signal check</em> to handle signal synchronously. Consider the
+two examples below.</p></div>
+<div class="paragraph"><p>Prevent a processing from taking too long</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>signal handle SIGALRM
+alarm 20
+try -signal {
+ .. possibly long running process ..
+ alarm 0
+} on signal {sig} {
+ puts stderr "Process took too long"
+}</tt></pre>
+</div></div>
+<div class="paragraph"><p>Handle SIGHUP to reconfigure:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>signal ignore SIGHUP
+while {1} {
+ ... handle configuration/reconfiguration ...
+ while {[signal check -clear SIGHUP] eq ""} {
+ ... do processing ..
+ }
+ # Received SIGHUP, so reconfigure
+}</tt></pre>
+</div></div>
+</div>
+<div class="sect2">
+<h3 id="_sleep">sleep</h3>
+<div class="paragraph"><p><tt><strong>sleep</strong> <em>seconds</em></tt></p></div>
+<div class="paragraph"><p>Pauses for the given number of seconds, which may be a floating
+point value less than one to sleep for less than a second, or an
+integer to sleep for one or more seconds.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_source">source</h3>
+<div class="paragraph"><p><tt><strong>source</strong> <em>fileName</em></tt></p></div>
+<div class="paragraph"><p>Read file <strong>fileName</strong> and pass the contents to the Tcl interpreter
+as a sequence of commands to execute in the normal fashion. The return
+value of <em>source</em> is the return value of the last command executed
+from the file. If an error occurs in executing the contents of the
+file, then the <em>source</em> command will return that error.</p></div>
+<div class="paragraph"><p>If a <em>return</em> command is invoked from within the file, the remainder of
+the file will be skipped and the <em>source</em> command will return
+normally with the result from the <em>return</em> command.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_split">split</h3>
+<div class="paragraph"><p><tt><strong>split</strong> <em>string ?splitChars?</em></tt></p></div>
+<div class="paragraph"><p>Returns a list created by splitting <strong>string</strong> at each character
+that is in the <strong>splitChars</strong> argument.</p></div>
+<div class="paragraph"><p>Each element of the result list will consist of the
+characters from <strong>string</strong> between instances of the
+characters in <strong>splitChars</strong>.</p></div>
+<div class="paragraph"><p>Empty list elements will be generated if <strong>string</strong> contains
+adjacent characters in <strong>splitChars</strong>, or if the first or last
+character of <strong>string</strong> is in <strong>splitChars</strong>.</p></div>
+<div class="paragraph"><p>If <strong>splitChars</strong> is an empty string then each character of
+<strong>string</strong> becomes a separate element of the result list.</p></div>
+<div class="paragraph"><p><strong>SplitChars</strong> defaults to the standard white-space characters.
+For example,</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>split "comp.unix.misc" .</tt></pre>
+</div></div>
+<div class="paragraph"><p>returns <tt><em>"comp unix misc"</em></tt> and</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>split "Hello world" {}</tt></pre>
+</div></div>
+<div class="paragraph"><p>returns <tt><em>"H e l l o { } w o r l d"</em></tt>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_stackdump">stackdump</h3>
+<div class="paragraph"><p><tt><strong>stackdump</strong> <em>stacktrace</em></tt></p></div>
+<div class="paragraph"><p>Creates a human readable representation of a stack trace.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_stacktrace">stacktrace</h3>
+<div class="paragraph"><p><tt><strong>stacktrace</strong></tt></p></div>
+<div class="paragraph"><p>Returns a live stack trace as a list of <tt>proc file line proc file line …</tt>.
+Iteratively uses <em>info frame</em> to create the stack trace. This stack trace is in the
+same form as produced by <em>catch</em> and <em>info stacktrace</em></p></div>
+<div class="paragraph"><p>See also <em>stackdump</em>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_string">string</h3>
+<div class="paragraph"><p><tt><strong>string</strong> <em>option arg ?arg …?</em></tt></p></div>
+<div class="paragraph"><p>Perform one of several string operations, depending on <strong>option</strong>.
+The legal options (which may be abbreviated) are:</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt><strong>string compare ?-nocase?</strong> <em>string1 string2</em></tt>
+</dt>
+<dd>
+<p>
+ Perform a character-by-character comparison of strings <strong>string1</strong> and
+ <strong>string2</strong> in the same way as the C <em>strcmp</em> procedure. Return
+ -1, 0, or 1, depending on whether <strong>string1</strong> is lexicographically
+ less than, equal to, or greater than <strong>string2</strong>.
+ Performs a case-insensitive comparison if <em>-nocase</em> is specified.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>string equal ?-nocase?</strong> <em>string1 string2</em></tt>
+</dt>
+<dd>
+<p>
+ Returns 1 if the strings are equal, or 0 otherwise.
+ Performs a case-insensitive comparison if <em>-nocase</em> is specified.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>string first</strong> <em>string1 string2 ?firstIndex?</em></tt>
+</dt>
+<dd>
+<p>
+ Search <strong>string2</strong> for a sequence of characters that exactly match
+ the characters in <strong>string1</strong>. If found, return the index of the
+ first character in the first such match within <strong>string2</strong>. If not
+ found, return -1. If <strong>firstIndex</strong> is specified, matching will start
+ from <strong>firstIndex</strong> of <strong>string1</strong>.
+</p>
+</dd>
+<dt class="hdlist1">
+
+</dt>
+<dd>
+<p>
+ See STRING AND LIST INDEX SPECIFICATIONS for all allowed forms for <strong>firstIndex</strong>.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>string index</strong> <em>string charIndex</em></tt>
+</dt>
+<dd>
+<p>
+ Returns the <strong>charIndex</strong>'th character of the <strong>string</strong>
+ argument. A <strong>charIndex</strong> of 0 corresponds to the first
+ character of the string.
+ If <strong>charIndex</strong> is less than 0 or greater than
+ or equal to the length of the string then an empty string is
+ returned.
+</p>
+</dd>
+<dt class="hdlist1">
+
+</dt>
+<dd>
+<p>
+ See STRING AND LIST INDEX SPECIFICATIONS for all allowed forms for <strong>charIndex</strong>.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>string is</strong> <em>class</em> ?<strong>-strict</strong>? <em>string</em></tt>
+</dt>
+<dd>
+<p>
+ Returns 1 if <strong>string</strong> is a valid member of the specified character
+ class, otherwise returns 0. If <em>-strict</em> is specified, then an
+ empty string returns 0, otherwise an empty string will return 1
+ on any class. The following character classes are recognized
+ (the class name can be abbreviated):
+</p>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt>alnum</tt>
+</dt>
+<dd>
+<p>
+Any alphabet or digit character.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>alpha</tt>
+</dt>
+<dd>
+<p>
+Any alphabet character.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>ascii</tt>
+</dt>
+<dd>
+<p>
+Any character with a value less than 128 (those that are in the 7-bit ascii range).
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>control</tt>
+</dt>
+<dd>
+<p>
+Any control character.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>digit</tt>
+</dt>
+<dd>
+<p>
+Any digit character.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>double</tt>
+</dt>
+<dd>
+<p>
+Any of the valid forms for a double in Tcl, with optional surrounding whitespace.
+ In case of under/overflow in the value, 0 is returned.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>graph</tt>
+</dt>
+<dd>
+<p>
+Any printing character, except space.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>integer</tt>
+</dt>
+<dd>
+<p>
+Any of the valid string formats for an integer value in Tcl, with optional surrounding whitespace.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>lower</tt>
+</dt>
+<dd>
+<p>
+Any lower case alphabet character.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>print</tt>
+</dt>
+<dd>
+<p>
+Any printing character, including space.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>punct</tt>
+</dt>
+<dd>
+<p>
+Any punctuation character.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>space</tt>
+</dt>
+<dd>
+<p>
+Any space character.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>upper</tt>
+</dt>
+<dd>
+<p>
+Any upper case alphabet character.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>xdigit</tt>
+</dt>
+<dd>
+<p>
+Any hexadecimal digit character ([0-9A-Fa-f]).
+</p>
+</dd>
+</dl></div>
+</dd>
+<dt class="hdlist1">
+<tt><strong>string last</strong> <em>string1 string2 ?lastIndex?</em></tt>
+</dt>
+<dd>
+<p>
+ Search <strong>string2</strong> for a sequence of characters that exactly match
+ the characters in <strong>string1</strong>. If found, return the index of the
+ first character in the last such match within <strong>string2</strong>. If there
+ is no match, then return -1. If <strong>lastIndex</strong> is specified, only characters
+ up to <strong>lastIndex</strong> of <strong>string2</strong> will be considered in the match.
+</p>
+</dd>
+<dt class="hdlist1">
+
+</dt>
+<dd>
+<p>
+ See STRING AND LIST INDEX SPECIFICATIONS for all allowed forms for <strong>lastIndex</strong>.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>string length</strong> <em>string</em></tt>
+</dt>
+<dd>
+<p>
+ Returns a decimal string giving the number of characters in <strong>string</strong>.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>string match ?-nocase?</strong> <em>pattern string</em></tt>
+</dt>
+<dd>
+<p>
+ See if <strong>pattern</strong> matches <strong>string</strong>; return 1 if it does, 0
+ if it doesn’t. Matching is done in a fashion similar to that
+ used by the C-shell. For the two strings to match, their contents
+ must be identical except that the following special sequences
+ may appear in <strong>pattern</strong>:
+</p>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt>*</tt>
+</dt>
+<dd>
+<p>
+ Matches any sequence of characters in <strong>string</strong>,
+ including a null string.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>?</tt>
+</dt>
+<dd>
+<p>
+ Matches any single character in <strong>string</strong>.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>[<strong>chars</strong>]</tt>
+</dt>
+<dd>
+<p>
+ Matches any character in the set given by <strong>chars</strong>.
+ If a sequence of the form <strong>x</strong>-<strong>y</strong> appears in <strong>chars</strong>,
+ then any character between <strong>x</strong> and <strong>y</strong>, inclusive,
+ will match.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>\x</tt>
+</dt>
+<dd>
+<p>
+ Matches the single character <strong>x</strong>. This provides a way of
+ avoiding the special interpretation of the characters `\*?[]\`
+ in <strong>pattern</strong>.
+</p>
+</dd>
+</dl></div>
+</dd>
+<dt class="hdlist1">
+
+</dt>
+<dd>
+<p>
+ Performs a case-insensitive comparison if <em>-nocase</em> is specified.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>string range</strong> <em>string first last</em></tt>
+</dt>
+<dd>
+<p>
+ Returns a range of consecutive characters from <strong>string</strong>, starting
+ with the character whose index is <strong>first</strong> and ending with the
+ character whose index is <strong>last</strong>. An index of 0 refers to the
+ first character of the string.
+</p>
+</dd>
+<dt class="hdlist1">
+
+</dt>
+<dd>
+<p>
+ See STRING AND LIST INDEX SPECIFICATIONS for all allowed forms for <strong>first</strong> and <strong>last</strong>.
+</p>
+</dd>
+<dt class="hdlist1">
+
+</dt>
+<dd>
+<p>
+ If <strong>first</strong> is less than zero then it is treated as if it were zero, and
+ if <strong>last</strong> is greater than or equal to the length of the string then
+ it is treated as if it were <em>end</em>. If <strong>first</strong> is greater than
+ <strong>last</strong> then an empty string is returned.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>string repeat</strong> <em>string count</em></tt>
+</dt>
+<dd>
+<p>
+ Returns a new string consisting of <strong>string</strong> repeated <strong>count</strong> times.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>string reverse</strong> <em>string</em></tt>
+</dt>
+<dd>
+<p>
+ Returns a string that is the same length as <strong>string</strong> but
+ with its characters in the reverse order.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>string tolower</strong> <em>string</em></tt>
+</dt>
+<dd>
+<p>
+ Returns a value equal to <strong>string</strong> except that all upper case
+ letters have been converted to lower case.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>string toupper</strong> <em>string</em></tt>
+</dt>
+<dd>
+<p>
+ Returns a value equal to <strong>string</strong> except that all lower case
+ letters have been converted to upper case.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>string trim</strong> <em>string ?chars?</em></tt>
+</dt>
+<dd>
+<p>
+ Returns a value equal to <strong>string</strong> except that any leading
+ or trailing characters from the set given by <strong>chars</strong> are
+ removed.
+ If <strong>chars</strong> is not specified then white space is removed
+ (spaces, tabs, newlines, and carriage returns).
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>string trimleft</strong> <em>string ?chars?</em></tt>
+</dt>
+<dd>
+<p>
+ Returns a value equal to <strong>string</strong> except that any
+ leading characters from the set given by <strong>chars</strong> are
+ removed.
+ If <strong>chars</strong> is not specified then white space is removed
+ (spaces, tabs, newlines, and carriage returns).
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>string trimright</strong> <em>string ?chars?</em></tt>
+</dt>
+<dd>
+<p>
+ Returns a value equal to <strong>string</strong> except that any
+ trailing characters from the set given by <strong>chars</strong> are
+ removed.
+ If <strong>chars</strong> is not specified then white space is removed
+ (spaces, tabs, newlines, and carriage returns).
+ Null characters are always removed.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_subst">subst</h3>
+<div class="paragraph"><p><tt><strong>subst ?-nobackslashes? ?-nocommands? ?-novariables?</strong> <em>string</em></tt></p></div>
+<div class="paragraph"><p>This command performs variable substitutions, command substitutions,
+and backslash substitutions on its string argument and returns the
+fully-substituted result. The substitutions are performed in exactly
+the same way as for Tcl commands. As a result, the string argument
+is actually substituted twice, once by the Tcl parser in the usual
+fashion for Tcl commands, and again by the subst command.</p></div>
+<div class="paragraph"><p>If any of the <strong>-nobackslashes</strong>, <strong>-nocommands</strong>, or <strong>-novariables</strong> are
+specified, then the corresponding substitutions are not performed.
+For example, if <strong>-nocommands</strong> is specified, no command substitution
+is performed: open and close brackets are treated as ordinary
+characters with no special interpretation.</p></div>
+<div class="paragraph"><p><strong>Note</strong>: when it performs its substitutions, subst does not give any
+special treatment to double quotes or curly braces. For example,
+the following script returns <em>xyz {44}</em>, not <em>xyz {$a}</em>.</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set a 44
+subst {xyz {$a}}</tt></pre>
+</div></div>
+</div>
+<div class="sect2">
+<h3 id="_switch">switch</h3>
+<div class="paragraph"><p><tt><strong>switch</strong> <em>?options? string pattern body ?pattern body …?</em></tt></p></div>
+<div class="paragraph"><p><tt><strong>switch</strong> <em>?options? string {pattern body ?pattern body …?}</em></tt></p></div>
+<div class="paragraph"><p>The <em>switch</em> command matches its string argument against each of
+the pattern arguments in order. As soon as it finds a pattern that
+matches string it evaluates the following body and returns the
+result of that evaluation. If the last pattern argument is default
+then it matches anything. If no pattern argument matches string and
+no default is given, then the switch command returns an empty string.
+If the initial arguments to switch start with - then they are treated
+as options. The following options are currently supported:</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt>-exact</tt>
+</dt>
+<dd>
+<p>
+ Use exact matching when comparing string to a
+ pattern. This is the default.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>-glob</tt>
+</dt>
+<dd>
+<p>
+ When matching string to the patterns, use glob-style
+ matching (i.e. the same as implemented by the string
+ match command).
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>-regexp</tt>
+</dt>
+<dd>
+<p>
+ When matching string to the patterns, use regular
+ expression matching (i.e. the same as implemented
+ by the regexp command).
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>-command <em>commandname</em></tt>
+</dt>
+<dd>
+<p>
+ When matching string to the patterns, use the given command, which
+ must be a single word. The command is invoked as
+ <em>commandname pattern string</em>, or <em>commandname -nocase pattern string</em>
+ and must return 1 if matched, or 0 if not.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>--</tt>
+</dt>
+<dd>
+<p>
+ Marks the end of options. The argument following
+ this one will be treated as string even if it starts
+ with a -.
+</p>
+</dd>
+</dl></div>
+<div class="paragraph"><p>Two syntaxes are provided for the pattern and body arguments. The
+first uses a separate argument for each of the patterns and commands;
+this form is convenient if substitutions are desired on some of the
+patterns or commands. The second form places all of the patterns
+and commands together into a single argument; the argument must
+have proper list structure, with the elements of the list being the
+patterns and commands. The second form makes it easy to construct
+multi-line switch commands, since the braces around the whole list
+make it unnecessary to include a backslash at the end of each line.
+Since the pattern arguments are in braces in the second form, no
+command or variable substitutions are performed on them; this makes
+the behavior of the second form different than the first form in
+some cases.</p></div>
+<div class="paragraph"><p>If a body is specified as <em>-</em> it means that the body for the next
+pattern should also be used as the body for this pattern (if the
+next pattern also has a body of “-” then the body after that is
+used, and so on). This feature makes it possible to share a single
+body among several patterns.</p></div>
+<div class="paragraph"><p>Below are some examples of switch commands:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>switch abc a - b {format 1} abc {format 2} default {format 3}</tt></pre>
+</div></div>
+<div class="paragraph"><p>will return 2,</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>switch -regexp aaab {
+ ^a.*b$ -
+ b {format 1}
+ a* {format 2}
+ default {format 3}
+}</tt></pre>
+</div></div>
+<div class="paragraph"><p>will return 1, and</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>switch xyz {
+ a -
+ b {format 1}
+ a* {format 2}
+ default {format 3}
+}</tt></pre>
+</div></div>
+<div class="paragraph"><p>will return 3.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_tailcall">tailcall</h3>
+<div class="paragraph"><p><tt><strong>tailcall</strong> <em>cmd ?arg…?</em></tt></p></div>
+<div class="paragraph"><p>The <em>tailcall</em> command provides an optimised way of invoking a command whilst replacing
+the current call frame. This is similar to <em>exec</em> in Bourne Shell.</p></div>
+<div class="paragraph"><p>The following are identical except the first immediately replaces the current call frame.</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>tailcall a b c</tt></pre>
+</div></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>return [uplevel 1 a b c]</tt></pre>
+</div></div>
+<div class="paragraph"><p><em>tailcall</em> is useful for a dispatch mechanism:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>proc a {cmd args} {
+ tailcall sub_$cmd {*}$args
+}
+proc sub_cmd1 ...
+proc sub_cmd2 ...</tt></pre>
+</div></div>
+</div>
+<div class="sect2">
+<h3 id="_tell">tell</h3>
+<div class="paragraph"><p><tt><strong>tell</strong> <em>fileId</em></tt></p></div>
+<div class="paragraph"><p><tt><em>fileId</em> <strong>tell</strong></tt></p></div>
+<div class="paragraph"><p>Returns a decimal string giving the current access position in
+<strong>fileId</strong>.</p></div>
+<div class="paragraph"><p><strong>fileId</strong> must have been the return value from a previous call to
+<em>open</em>, or it may be <em>stdin</em>, <em>stdout</em>, or <em>stderr</em> to refer to one
+of the standard I/O channels.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_throw">throw</h3>
+<div class="paragraph"><p><tt><strong>throw</strong> <em>code ?msg?</em></tt></p></div>
+<div class="paragraph"><p>This command throws an exception (return) code along with an optional message.
+This command is mostly for convenient usage with <em>try</em>.</p></div>
+<div class="paragraph"><p>The command <tt>throw break</tt> is equivalent to <tt>break</tt>.
+The command <tt>throw 20 message</tt> can be caught with an <tt>on 20 …</tt> clause to <em>try</em>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_time">time</h3>
+<div class="paragraph"><p><tt><strong>time</strong> <em>command ?count?</em></tt></p></div>
+<div class="paragraph"><p>This command will call the Tcl interpreter <strong>count</strong>
+times to execute <strong>command</strong> (or once if <strong>count</strong> isn’t
+specified). It will then return a string of the form</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>503 microseconds per iteration</tt></pre>
+</div></div>
+<div class="paragraph"><p>which indicates the average amount of time required per iteration,
+in microseconds.</p></div>
+<div class="paragraph"><p>Time is measured in elapsed time, not CPU time.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_try">try</h3>
+<div class="paragraph"><p><tt><strong>try</strong> <em>?catchopts? tryscript</em> ?<strong>on</strong> <em>returncodes {?resultvar? ?optsvar?} handlerscript …</em>? ?<strong>finally</strong> <em>finalscript</em>?</tt></p></div>
+<div class="paragraph"><p>The <em>try</em> command is provided as a convenience for exception handling.</p></div>
+<div class="paragraph"><p>This interpeter first evaluates <strong>tryscript</strong> under the effect of the catch
+options <strong>catchopts</strong> (e.g. <tt>-signal -noexit --</tt>, see <em>catch</em>).</p></div>
+<div class="paragraph"><p>It then evaluates the script for the first matching <em>on</em> handler
+(there many be zero or more) based on the return code from the <em>try</em>
+section. For example a normal <tt>JIM_ERR</tt> error will be matched by
+an <em>on error</em> handler.</p></div>
+<div class="paragraph"><p>Finally, any <strong>finalscript</strong> is evaluated.</p></div>
+<div class="paragraph"><p>The result of this command is the result of <strong>tryscript</strong>, except in the
+case where an exception occurs in a matching <em>on</em> handler script or the <em>finally</em> script,
+in which case the result is this new exception.</p></div>
+<div class="paragraph"><p>The specified <strong>returncodes</strong> is a list of return codes either as names (<em>ok</em>, <em>error</em>, <em>break</em>, etc.)
+or as integers.</p></div>
+<div class="paragraph"><p>If <strong>resultvar</strong> and <strong>optsvar</strong> are specified, they are set as for <em>catch</em> before evaluating
+the matching handler.</p></div>
+<div class="paragraph"><p>For example:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set f [open input]
+try -signal {
+ process $f
+} on {continue break} {} {
+ error "Unexpected break/continue"
+} on error {msg opts} {
+ puts "Dealing with error"
+ return {*}$opts $msg
+} on signal sig {
+ puts "Got signal: $sig"
+} finally {
+ $f close
+}</tt></pre>
+</div></div>
+<div class="paragraph"><p>If break, continue or error are raised, they are dealt with by the matching
+handler.</p></div>
+<div class="paragraph"><p>In any case, the file will be closed via the <em>finally</em> clause.</p></div>
+<div class="paragraph"><p>See also <em>throw</em>, <em>catch</em>, <em>return</em>, <em>error</em>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_unknown">unknown</h3>
+<div class="paragraph"><p><tt><strong>unknown</strong> <em>cmdName ?arg arg …?</em></tt></p></div>
+<div class="paragraph"><p>This command doesn’t actually exist as part of Tcl, but Tcl will
+invoke it if it does exist.</p></div>
+<div class="paragraph"><p>If the Tcl interpreter encounters a command name for which there
+is not a defined command, then Tcl checks for the existence of
+a command named <em>unknown</em>.</p></div>
+<div class="paragraph"><p>If there is no such command, then the interpeter returns an
+error.</p></div>
+<div class="paragraph"><p>If the <em>unknown</em> command exists, then it is invoked with
+arguments consisting of the fully-substituted name and arguments
+for the original non-existent command.</p></div>
+<div class="paragraph"><p>The <em>unknown</em> command typically does things like searching
+through library directories for a command procedure with the name
+<strong>cmdName</strong>, or expanding abbreviated command names to full-length,
+or automatically executing unknown commands as UNIX sub-processes.</p></div>
+<div class="paragraph"><p>In some cases (such as expanding abbreviations) <em>unknown</em> will
+change the original command slightly and then (re-)execute it.
+The result of the <em>unknown</em> command is used as the result for
+the original non-existent command.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_unset">unset</h3>
+<div class="paragraph"><p><tt><strong>unset ?-nocomplain? ?--?</strong> <em>?name name …?</em></tt></p></div>
+<div class="paragraph"><p>Remove variables.
+Each <strong>name</strong> is a variable name, specified in any of the
+ways acceptable to the <em>set</em> command.</p></div>
+<div class="paragraph"><p>If a <strong>name</strong> refers to an element of an array, then that
+element is removed without affecting the rest of the array.</p></div>
+<div class="paragraph"><p>If a <strong>name</strong> consists of an array name with no parenthesized
+index, then the entire array is deleted.</p></div>
+<div class="paragraph"><p>The <em>unset</em> command returns an empty string as result.</p></div>
+<div class="paragraph"><p>An error occurs if any of the variables doesn’t exist, unless <em>-nocomplain</em>
+is specified. The <em>--</em> argument may be specified to stop option processing
+in case the variable name may be <em>-nocomplain</em>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_uplevel">uplevel</h3>
+<div class="paragraph"><p><tt><strong>uplevel</strong> <em>?level? command ?command …?</em></tt></p></div>
+<div class="paragraph"><p>All of the <strong>command</strong> arguments are concatenated as if they had
+been passed to <em>concat</em>; the result is then evaluated in the
+variable context indicated by <strong>level</strong>. <em>Uplevel</em> returns
+the result of that evaluation. If <strong>level</strong> is an integer, then
+it gives a distance (up the procedure calling stack) to move before
+executing the command. If <strong>level</strong> consists of <em>#</em> followed by
+a number then the number gives an absolute level number. If <strong>level</strong>
+is omitted then it defaults to <em>1</em>. <strong>Level</strong> cannot be
+defaulted if the first <strong>command</strong> argument starts with a digit or <em>\#</em>.</p></div>
+<div class="paragraph"><p>For example, suppose that procedure <em>a</em> was invoked
+from top-level, and that it called <em>b</em>, and that <em>b</em> called <em>c</em>.
+Suppose that <em>c</em> invokes the <em>uplevel</em> command. If <strong>level</strong>
+is <em>1</em> or <em>\#2</em> or omitted, then the command will be executed
+in the variable context of <em>b</em>. If <strong>level</strong> is <em>2</em> or <em>\#1</em>
+then the command will be executed in the variable context of <em>a</em>.</p></div>
+<div class="paragraph"><p>If <strong>level</strong> is <em>3</em> or <em>\#0</em> then the command will be executed
+at top-level (only global variables will be visible).
+The <em>uplevel</em> command causes the invoking procedure to disappear
+from the procedure calling stack while the command is being executed.
+In the above example, suppose <em>c</em> invokes the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>uplevel 1 {set x 43; d}</tt></pre>
+</div></div>
+<div class="paragraph"><p>where <em>d</em> is another Tcl procedure. The <em>set</em> command will
+modify the variable <em>x</em> in <em>b’s context, and 'd</em> will execute
+at level 3, as if called from <em>b</em>. If it in turn executes
+the command</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>uplevel {set x 42}</tt></pre>
+</div></div>
+<div class="paragraph"><p>then the <em>set</em> command will modify the same variable <em>x</em> in <em>b’s
+context: the procedure 'c</em> does not appear to be on the call stack
+when <em>d</em> is executing. The command <em>info level</em> may
+be used to obtain the level of the current procedure.</p></div>
+<div class="paragraph"><p><em>Uplevel</em> makes it possible to implement new control
+constructs as Tcl procedures (for example, <em>uplevel</em> could
+be used to implement the <em>while</em> construct as a Tcl procedure).</p></div>
+</div>
+<div class="sect2">
+<h3 id="_upvar">upvar</h3>
+<div class="paragraph"><p><tt><strong>upvar</strong> <em>?level? otherVar myVar ?otherVar myVar …?</em></tt></p></div>
+<div class="paragraph"><p>This command arranges for one or more local variables in the current
+procedure to refer to variables in an enclosing procedure call or
+to global variables.</p></div>
+<div class="paragraph"><p><strong>Level</strong> may have any of the forms permitted for the <em>uplevel</em>
+command, and may be omitted if the first letter of the first <strong>otherVar</strong>
+isn’t <em>\#</em> or a digit (it defaults to <em>1</em>).</p></div>
+<div class="paragraph"><p>For each <strong>otherVar</strong> argument, <em>upvar</em> makes the variable
+by that name in the procedure frame given by <strong>level</strong> (or at
+global level, if <strong>level</strong> is <em>\#0</em>) accessible
+in the current procedure by the name given in the corresponding
+<strong>myVar</strong> argument.</p></div>
+<div class="paragraph"><p>The variable named by <strong>otherVar</strong> need not exist at the time of the
+call; it will be created the first time <strong>myVar</strong> is referenced, just like
+an ordinary variable.</p></div>
+<div class="paragraph"><p><em>Upvar</em> may only be invoked from within procedures.</p></div>
+<div class="paragraph"><p><em>Upvar</em> returns an empty string.</p></div>
+<div class="paragraph"><p>The <em>upvar</em> command simplifies the implementation of call-by-name
+procedure calling and also makes it easier to build new control constructs
+as Tcl procedures.
+For example, consider the following procedure:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>proc add2 name {
+ upvar $name x
+ set x [expr $x+2]
+}</tt></pre>
+</div></div>
+<div class="paragraph"><p><em>Add2</em> is invoked with an argument giving the name of a variable,
+and it adds two to the value of that variable.
+Although <em>add2</em> could have been implemented using <em>uplevel</em>
+instead of <em>upvar</em>, <em>upvar</em> makes it simpler for <em>add2</em>
+to access the variable in the caller’s procedure frame.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_while">while</h3>
+<div class="paragraph"><p><tt><strong>while</strong> <em>test body</em></tt></p></div>
+<div class="paragraph"><p>The <strong>while</strong> command evaluates <strong>test</strong> as an expression
+(in the same way that <em>expr</em> evaluates its argument).
+The value of the expression must be numeric; if it is non-zero
+then <strong>body</strong> is executed by passing it to the Tcl interpreter.</p></div>
+<div class="paragraph"><p>Once <strong>body</strong> has been executed then <strong>test</strong> is evaluated
+again, and the process repeats until eventually <strong>test</strong>
+evaluates to a zero numeric value. <em>Continue</em>
+commands may be executed inside <strong>body</strong> to terminate the current
+iteration of the loop, and <em>break</em>
+commands may be executed inside <strong>body</strong> to cause immediate
+termination of the <em>while</em> command.</p></div>
+<div class="paragraph"><p>The <em>while</em> command always returns an empty string.</p></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_optional_extensions">OPTIONAL-EXTENSIONS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>The following extensions may or may not be available depending upon
+what options were selected when Jim Tcl was built.</p></div>
+<div class="sect2">
+<h3 id="_bio">bio</h3>
+<div class="paragraph"><p>The bio command provides a way to read and write binary files
+from within Tcl. Note that since Jim supports binary strings, the
+main use of this command is <em>bio copy</em> to easily copy between file
+descriptors.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt><strong>bio read ?-hex?</strong> <em>fd var numbytes</em></tt>
+</dt>
+<dd>
+<p>
+ Read bytes from a file descriptor. By default the data is not encoded.
+ Using <strong>-hex</strong> encodes the data as ascii hex instead. Returns
+ the number of bytes actually read.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>bio write ?-hex?</strong> <em>fd buf</em></tt>
+</dt>
+<dd>
+<p>
+ Write a string to a file descriptor. If <strong>-hex</strong> is specified, the
+ string is expected to be in ascii hexx format. Returns the number
+ of bytes actually written.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>bio copy</strong> <em>fromfd tofd ?numbytes?</em></tt>
+</dt>
+<dd>
+<p>
+ Copy binary data from the file descriptor <strong>fromfd</strong> to the
+ file descriptor <strong>tofd</strong>. If <strong>numbytes</strong> is specified, at most that many
+ bytes will be copied. Otherwise copying continues until the end
+ of the input file. Returns the number of bytes actually copied.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_posix_os_fork_os_wait_os_gethostname_os_getids_os_uptime">posix: os.fork, os.wait, os.gethostname, os.getids, os.uptime</h3>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt><strong>os.fork</strong></tt>
+</dt>
+<dd>
+<p>
+ Invokes <em>fork(2)</em> and returns the result.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>os.wait -nohang</strong> <em>pid</em></tt>
+</dt>
+<dd>
+<p>
+ Invokes waitpid(2), with WNOHANG if <strong>-nohang</strong> is specified.
+ Returns a list of 3 elements.
+</p>
+<div class="literalblock">
+<div class="content">
+<pre><tt>{0 none 0} if -nohang is specified, and the process is still alive.</tt></pre>
+</div></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>{-1 error <error-description>} if the process does not exist or has already been waited for.</tt></pre>
+</div></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>{<pid> exit <exit-status>} if the process exited normally.</tt></pre>
+</div></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>{<pid> signal <signal-number>} if the process terminated on a signal.</tt></pre>
+</div></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>{<pid> other 0} otherwise (core dump, stopped, continued, etc.)</tt></pre>
+</div></div>
+</dd>
+<dt class="hdlist1">
+<tt><strong>os.gethostname</strong></tt>
+</dt>
+<dd>
+<p>
+ Invokes <em>gethostname(3)</em> and returns the result.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>os.getids</strong></tt>
+</dt>
+<dd>
+<p>
+ Returns the various user/group ids for the current process.
+</p>
+<div class="literalblock">
+<div class="content">
+<pre><tt>jim> os.getids
+uid 1000 euid 1000 gid 100 egid 100</tt></pre>
+</div></div>
+</dd>
+<dt class="hdlist1">
+<tt><strong>os.uptime</strong></tt>
+</dt>
+<dd>
+<p>
+ Returns the number of seconds since system boot. See description of <em>uptime</em> in <em>sysinfo(2)</em>.
+</p>
+</dd>
+</dl></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_ansi_i_o_aio_and_eventloop_api">ANSI I/O (aio) and EVENTLOOP API</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Jim provides an alternative object-based API for I/O.</p></div>
+<div class="paragraph"><p>See <em><a href="#_open">open</a></em> and <em><a href="#_socket">socket</a></em> for commands which return an I/O handle.</p></div>
+<div class="sect2">
+<h3 id="_aio">aio</h3>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt>$handle <strong>read ?-nonewline?</strong> <em>?len?</em></tt>
+</dt>
+<dd>
+<p>
+ Read and return bytes from the stream. To eof if no len.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>$handle <strong>gets</strong> <em>?var?</em></tt>
+</dt>
+<dd>
+<p>
+ Read one line and return it or store it in the var
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>$handle <strong>puts ?-nonewline?</strong> <em>str</em></tt>
+</dt>
+<dd>
+<p>
+ Write the string, with newline unless -nonewline
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>$handle <strong>flush</strong></tt>
+</dt>
+<dd>
+<p>
+ Flush the stream
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>$handle <strong>eof</strong></tt>
+</dt>
+<dd>
+<p>
+ Returns 1 if stream is at eof
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>$handle <strong>close</strong></tt>
+</dt>
+<dd>
+<p>
+ Closes the stream
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>$handle <strong>seek</strong> <em>offset</em> <strong>?start|current|end?</strong></tt>
+</dt>
+<dd>
+<p>
+ Seeks in the stream (default <em>current</em>)
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>$handle <strong>tell</strong></tt>
+</dt>
+<dd>
+<p>
+ Returns the current seek position
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>$handle <strong>ndelay ?0|1?</strong></tt>
+</dt>
+<dd>
+<p>
+ Set O_NDELAY (if arg). Returns current/new setting.
+ Note that in general ANSI I/O interacts badly with non-blocking I/O.
+ Use with care.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>$handle <strong>accept</strong></tt>
+</dt>
+<dd>
+<p>
+ Server socket only: Accept a connection and return stream
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>$handle <strong>sendto</strong> <em>str ?hostname:?port</em></tt>
+</dt>
+<dd>
+<p>
+ Sends the string, <strong>str</strong>, to the given address via the socket using sendto(2).
+ This is intended for udp sockets and may give an error or behave in unintended
+ ways for other handle types.
+ Returns the number of bytes written.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>$handle <strong>recvfrom</strong> <em>maxlen ?addrvar?</em></tt>
+</dt>
+<dd>
+<p>
+ Receives a message from the handle via recvfrom(2) and returns it.
+ At most <strong>maxlen</strong> bytes are read.
+ If <strong>addrvar</strong> is specified, the sending address of the message is stored in
+ the named variable in the form <em>addr:port</em>. See <em>socket</em> for details.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_eventloop_after_vwait_update">eventloop: after, vwait, update</h3>
+<div class="paragraph"><p>The following commands allow a script to be invoked when the given condition occurs.
+If no script is given, returns the current script. If the given script is the empty, the
+handler is removed.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt>$handle <strong>readable</strong> <em>?readable-script?</em></tt>
+</dt>
+<dd>
+<p>
+ Sets or returns the script for when the socket is readable.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>$handle <strong>writable</strong> <em>?writable-script?</em></tt>
+</dt>
+<dd>
+<p>
+ Sets or returns the script for when the socket is writable.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>$handle <strong>onexception</strong> <em>?exception-script?</em></tt>
+</dt>
+<dd>
+<p>
+ Sets or returns the script for when when oob data received.
+</p>
+</dd>
+</dl></div>
+<div class="paragraph"><p>For compatibility with <em>Tcl</em>, these may be prefixed with <em>fileevent</em>. e.g.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+
+</dt>
+<dd>
+<p>
+ <tt>fileevent $handle <strong>readable</strong> <em>…</em></tt>
+</p>
+</dd>
+</dl></div>
+<div class="paragraph"><p>Time-based execution is also available via the eventloop API.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt><strong>after</strong> <em>ms</em></tt>
+</dt>
+<dd>
+<p>
+ Sleeps for the given number of milliseconds. No events are
+ processed during this time.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>after</strong> <em>ms|<strong>idle</strong> script ?script …?</em></tt>
+</dt>
+<dd>
+<p>
+ The scripts are concatenated and executed after the given
+ number of milliseconds have elapsed. If <em>idle</em> is specified,
+ the script will run the next time the event loop is processed
+ with <em>vwait</em> or <em>update</em>. The script is only run once and
+ then removed. Returns an event id.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>after cancel</strong> <em>id|command</em></tt>
+</dt>
+<dd>
+<p>
+ Cancels an <em>after</em> event with the given event id or matching
+ command (script). Returns the number of milliseconds
+ remaining until the event would have fired. Returns the
+ empty string if no matching event is found.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>after info</strong> <em>?id?</em></tt>
+</dt>
+<dd>
+<p>
+ If <strong>id</strong> is not given, returns a list of current <em>after</em>
+ events. If <strong>id</strong> is given, returns a list containing the
+ associated script and either <em>timer</em> or <em>idle</em> to indicated
+ the type of the event. An error occurs if <strong>id</strong> does not
+ match an event.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>vwait</strong> <em>variable</em></tt>
+</dt>
+<dd>
+<p>
+ A call to <em>vwait</em> is enters the eventloop. <em>vwait</em> processes
+ events until the named (global) variable changes or all
+ event handlers are removed. The variable need not exist
+ beforehand. If there are no event handlers defined, <em>vwait</em>
+ returns immediately.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>update ?idletasks?</strong></tt>
+</dt>
+<dd>
+<p>
+ A call to <em>update</em> enters the eventloop to process expired events, but
+ no new events. If <em>idletasks</em> is specified, only expired time events are handled,
+ not file events.
+ Returns once handlers have been run for all expired events.
+</p>
+</dd>
+</dl></div>
+<div class="paragraph"><p>Scripts are executed at the global scope. If an error occurs during a handler script,
+an attempt is made to call (the user-defined command) <em>bgerror</em> with the details of the error.
+If the <em>bgerror</em> commands does not exist, it is printed to stderr instead.</p></div>
+<div class="paragraph"><p>If a file event handler script generates an error, the handler is automatically removed
+to prevent infinite errors. (A time event handler is always removed after execution).</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt><strong>bgerror</strong> <em>error</em></tt>
+</dt>
+<dd>
+<p>
+ Called when an event handler script generates an error.
+</p>
+</dd>
+</dl></div>
+</div>
+<div class="sect2">
+<h3 id="_socket">socket</h3>
+<div class="paragraph"><p>Various socket types may be created.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt><strong>socket unix</strong> <em>path</em></tt>
+</dt>
+<dd>
+<p>
+ A unix domain socket client.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>socket unix.server</strong> <em>path</em></tt>
+</dt>
+<dd>
+<p>
+ A unix domain socket server.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>socket ?-ipv6? stream</strong> <em>addr:port</em></tt>
+</dt>
+<dd>
+<p>
+ A TCP socket client.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt>*socket ?-ipv6? stream.server <em>?addr:?port</em></tt>
+</dt>
+<dd>
+<p>
+ A TCP socket server (<strong>addr</strong> defaults to 0.0.0.0 for IPv4 or [::] for IPv6).
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>socket ?-ipv6? dgram</strong> ?<em>addr:port</em>?</tt>
+</dt>
+<dd>
+<p>
+ A UDP socket client. If the address is not specified,
+ the client socket will be unbound and <em>sendto</em> must be used
+ to indicated the destination.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>socket ?-ipv6? dgram.server</strong> <em>addr:port</em></tt>
+</dt>
+<dd>
+<p>
+ A UDP socket server.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>socket pipe</strong></tt>
+</dt>
+<dd>
+<p>
+ A pipe. Note that unlike all other socket types, this command returns
+ a list of two channels: {read write}
+</p>
+</dd>
+</dl></div>
+<div class="paragraph"><p>This command creates a socket connected (client) or bound (server) to the given
+address.</p></div>
+<div class="paragraph"><p>The returned value is channel and may generally be used with the various file I/O
+commands (gets, puts, read, etc.), either as object-based syntax or Tcl-compatible syntax.</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set f [socket stream www.google.com:80]
+aio.sockstream1
+$f puts -nonewline "GET / HTTP/1.0\r\n\r\n"
+$f gets
+HTTP/1.0 302 Found
+$f close</tt></pre>
+</div></div>
+<div class="paragraph"><p>Server sockets, however support only <em>accept</em>, which is most useful in conjunction with
+the EVENTLOOP API.</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>set f [socket stream.server 80]
+$f readable {
+ set client [$f accept]
+ $client gets $buf
+ ...
+ $client puts -nonewline "HTTP/1.1 404 Not found\r\n"
+ $client close
+}
+vwait done</tt></pre>
+</div></div>
+<div class="paragraph"><p>The address, <strong>addr</strong>, can be given in one of the following forms:</p></div>
+<div class="olist arabic"><ol class="arabic">
+<li>
+<p>
+For IPv4 socket types, an IPv4 address such as 192.168.1.1
+</p>
+</li>
+<li>
+<p>
+For IPv6 socket types, an IPv6 address such as [fe80::1234] or [::]
+</p>
+</li>
+<li>
+<p>
+A hostname
+</p>
+</li>
+</ol></div>
+<div class="paragraph"><p>Note that on many systems, listening on an IPv6 address such as [::] will
+also accept requests via IPv4.</p></div>
+<div class="paragraph"><p>Where a hostname is specified, the <strong>first</strong> returned address is used
+which matches the socket type is used.</p></div>
+<div class="paragraph"><p>The special type <em>pipe</em> isn’t really a socket.</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>lassign [socket pipe] r w</tt></pre>
+</div></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt># Must close $w after exec
+exec ps >@$w &
+$w close</tt></pre>
+</div></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>$r readable ...</tt></pre>
+</div></div>
+</div>
+<div class="sect2">
+<h3 id="_syslog">syslog</h3>
+<div class="paragraph"><p><tt><strong>syslog</strong> <em>?options? ?priority? message</em></tt></p></div>
+<div class="paragraph"><p>This command sends message to system syslog facility with given
+priority. Valid priorities are:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>emerg, alert, crit, err, error, warning, notice, info, debug</tt></pre>
+</div></div>
+<div class="paragraph"><p>If a message is specified, but no priority is specified, then a
+priority of info is used.</p></div>
+<div class="paragraph"><p>By default, facility user is used and the value of global tcl variable
+argv0 is used as ident string. However, any of the following options
+may be specified before priority to control these parameters:</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt><strong>-facility</strong> <em>value</em></tt>
+</dt>
+<dd>
+<p>
+ Use specified facility instead of user. The following
+ values for facility are recognized:
+</p>
+<div class="literalblock">
+<div class="content">
+<pre><tt>authpriv, cron, daemon, kernel, lpr, mail, news, syslog, user,
+uucp, local0-local7</tt></pre>
+</div></div>
+</dd>
+<dt class="hdlist1">
+<tt><strong>-ident</strong> <em>string</em></tt>
+</dt>
+<dd>
+<p>
+ Use given string instead of argv0 variable for ident string.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>-options</strong> <em>integer</em></tt>
+</dt>
+<dd>
+<p>
+ Set syslog options such as <tt>LOG_CONS</tt>, <tt>LOG_NDELAY</tt>. You should
+ use numeric values of those from your system syslog.h file,
+ because I haven’t got time to implement yet another hash
+ table.
+</p>
+</dd>
+</dl></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="BuiltinVariables">BUILT-IN VARIABLES</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>The following global variables are created automatically
+by the Tcl library.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt><strong>env</strong></tt>
+</dt>
+<dd>
+<p>
+ This variable is set by Jim as an array
+ whose elements are the environment variables for the process.
+ Reading an element will return the value of the corresponding
+ environment variable.
+ This array is initialised at startup from the <em>env</em> command.
+ It may be modified and will affect the environment passed to
+ commands invoked with <em>exec</em>.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>auto_path</strong></tt>
+</dt>
+<dd>
+<p>
+ This variable contains a list of paths to search for packages.
+ It contains {. /lib/jim} by default.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>errorCode</strong></tt>
+</dt>
+<dd>
+<p>
+ This variable holds the value of the -errorcode return
+ option set by the most recent error that occurred in this
+ interpreter. This list value represents additional information
+ about the error in a form that is easy to process with
+ programs. The first element of the list identifies a general
+ class of errors, and determines the format of the rest of
+ the list. The following formats for -errorcode return options
+ are used by the Tcl core; individual applications may define
+ additional formats. Currently only <em>exec</em> sets this variable.
+ Otherwise it will be <strong>NONE</strong>.
+</p>
+</dd>
+</dl></div>
+<div class="paragraph"><p>The following global variables are set by jimsh.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<tt><strong>tcl_interactive</strong></tt>
+</dt>
+<dd>
+<p>
+ This variable is set to 1 if jimsh is started in interactive mode
+ or 0 otherwise.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>argv0</strong></tt>
+</dt>
+<dd>
+<p>
+ If jimsh is invoked to run a script, this variable contains the name
+ of the script.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>argv</strong></tt>
+</dt>
+<dd>
+<p>
+ If jimsh is invoked to run a script, this variable contains a list
+ of any arguments supplied to the script.
+</p>
+</dd>
+<dt class="hdlist1">
+<tt><strong>jim_argv0</strong></tt>
+</dt>
+<dd>
+<p>
+ The value of argv[0] when jimsh was invoked.
+</p>
+</dd>
+</dl></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_licence">LICENCE</h2>
+<div class="sectionbody">
+<div class="literalblock">
+<div class="content">
+<pre><tt>Copyright 2005 Salvatore Sanfilippo <antirez@invece.org>
+Copyright 2005 Clemens Hintze <c.hintze@gmx.net>
+Copyright 2005 patthoyts - Pat Thoyts <patthoyts@users.sf.net>
+Copyright 2008 oharboe - Oyvind Harboe - oyvind.harboe@zylin.com
+Copyright 2008 Andrew Lunn <andrew@lunn.ch>
+Copyright 2008 Duane Ellis <openocd@duaneellis.com>
+Copyright 2008 Uwe Klein <uklein@klein-messgeraete.de>
+Copyright 2009 Steve Bennett <steveb@workware.net.au></tt></pre>
+</div></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>The FreeBSD license</tt></pre>
+</div></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above
+ copyright notice, this list of conditions and the following
+ disclaimer in the documentation and/or other materials
+ provided with the distribution.</tt></pre>
+</div></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>THIS SOFTWARE IS PROVIDED BY THE JIM TCL PROJECT ``AS IS'' AND ANY
+EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
+PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
+JIM TCL PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
+ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.</tt></pre>
+</div></div>
+<div class="literalblock">
+<div class="content">
+<pre><tt>The views and conclusions contained in the software and documentation
+are those of the authors and should not be interpreted as representing
+official policies, either expressed or implied, of the Jim Tcl Project.</tt></pre>
+</div></div>
+</div>
+</div>
+</div>
+<div id="footnotes"><hr /></div>
+<div id="footer">
+<div id="footer-text">
+Last updated 2010-10-09 08:25:40 EST
+</div>
+</div>
+</body>
+</html>
@@ -1,13 +1,13 @@ #! /bin/sh # Guess values for system-dependent variables and create Makefiles. -# Generated by GNU Autoconf 2.65 for jim 0.63. +# Generated by GNU Autoconf 2.68 for jim 0.63. # # Report bugs to <steveb@workware.net.au>. # # # Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001, -# 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, -# Inc. +# 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 Free Software +# Foundation, Inc. # # # This configure script is free software; the Free Software Foundation @@ -91,6 +91,7 @@ fi IFS=" "" $as_nl" # Find who we are. Look in the path if we contain no directory separator. +as_myself= case $0 in #(( *[\\/]* ) as_myself=$0 ;; *) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR @@ -216,11 +217,18 @@ IFS=$as_save_IFS # We cannot yet assume a decent shell, so we have to provide a # neutralization value for shells without unset; and this also # works around shells that cannot unset nonexistent variables. + # Preserve -v and -x to the replacement shell. BASH_ENV=/dev/null ENV=/dev/null (unset BASH_ENV) >/dev/null 2>&1 && unset BASH_ENV ENV export CONFIG_SHELL - exec "$CONFIG_SHELL" "$as_myself" ${1+"$@"} + case $- in # (((( + *v*x* | *x*v* ) as_opts=-vx ;; + *v* ) as_opts=-v ;; + *x* ) as_opts=-x ;; + * ) as_opts= ;; + esac + exec "$CONFIG_SHELL" $as_opts "$as_myself" ${1+"$@"} fi if test x$as_have_required = xno; then : @@ -319,7 +327,7 @@ $as_echo X"$as_dir" | test -d "$as_dir" && break done test -z "$as_dirs" || eval "mkdir $as_dirs" - } || test -d "$as_dir" || as_fn_error "cannot create directory $as_dir" + } || test -d "$as_dir" || as_fn_error $? "cannot create directory $as_dir" } # as_fn_mkdir_p @@ -359,19 +367,19 @@ else fi # as_fn_arith -# as_fn_error ERROR [LINENO LOG_FD] -# --------------------------------- +# as_fn_error STATUS ERROR [LINENO LOG_FD] +# ---------------------------------------- # Output "`basename $0`: error: ERROR" to stderr. If LINENO and LOG_FD are # provided, also output the error to LOG_FD, referencing LINENO. Then exit the -# script with status $?, using 1 if that was 0. +# script with STATUS, using 1 if that was 0. as_fn_error () { - as_status=$?; test $as_status -eq 0 && as_status=1 - if test "$3"; then - as_lineno=${as_lineno-"$2"} as_lineno_stack=as_lineno_stack=$as_lineno_stack - $as_echo "$as_me:${as_lineno-$LINENO}: error: $1" >&$3 + as_status=$1; test $as_status -eq 0 && as_status=1 + if test "$4"; then + as_lineno=${as_lineno-"$3"} as_lineno_stack=as_lineno_stack=$as_lineno_stack + $as_echo "$as_me:${as_lineno-$LINENO}: error: $2" >&$4 fi - $as_echo "$as_me: error: $1" >&2 + $as_echo "$as_me: error: $2" >&2 as_fn_exit $as_status } # as_fn_error @@ -533,7 +541,7 @@ test -n "$DJDIR" || exec 7<&0 </dev/null exec 6>&1 # Name of the host. -# hostname on some systems (SVR3.2, Linux) returns a bogus exit status, +# hostname on some systems (SVR3.2, old GNU/Linux) returns a bogus exit status, # so uname gets run too. ac_hostname=`(hostname || uname -n) 2>/dev/null | sed 1q` @@ -600,6 +608,7 @@ SRCDIR EXTRA_CFLAGS JIM_LIBTYPE JIM_EXTENSIONS +CROSS SH_LDFLAGS SH_CFLAGS host_os @@ -613,6 +622,7 @@ build EGREP GREP CPP +DEFINE_HAVE_LONG_LONG SET_MAKE OBJEXT EXEEXT @@ -676,7 +686,8 @@ CFLAGS LDFLAGS LIBS CPPFLAGS -CPP' +CPP +CPPFLAGS' # Initialize some variables set by options. @@ -739,8 +750,9 @@ do fi case $ac_option in - *=*) ac_optarg=`expr "X$ac_option" : '[^=]*=\(.*\)'` ;; - *) ac_optarg=yes ;; + *=?*) ac_optarg=`expr "X$ac_option" : '[^=]*=\(.*\)'` ;; + *=) ac_optarg= ;; + *) ac_optarg=yes ;; esac # Accept the important Cygnus configure options, so we can diagnose typos. @@ -785,7 +797,7 @@ do ac_useropt=`expr "x$ac_option" : 'x-*disable-\(.*\)'` # Reject names that are not valid shell variable names. expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null && - as_fn_error "invalid feature name: $ac_useropt" + as_fn_error $? "invalid feature name: $ac_useropt" ac_useropt_orig=$ac_useropt ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'` case $ac_user_opts in @@ -811,7 +823,7 @@ do ac_useropt=`expr "x$ac_option" : 'x-*enable-\([^=]*\)'` # Reject names that are not valid shell variable names. expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null && - as_fn_error "invalid feature name: $ac_useropt" + as_fn_error $? "invalid feature name: $ac_useropt" ac_useropt_orig=$ac_useropt ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'` case $ac_user_opts in @@ -1015,7 +1027,7 @@ do ac_useropt=`expr "x$ac_option" : 'x-*with-\([^=]*\)'` # Reject names that are not valid shell variable names. expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null && - as_fn_error "invalid package name: $ac_useropt" + as_fn_error $? "invalid package name: $ac_useropt" ac_useropt_orig=$ac_useropt ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'` case $ac_user_opts in @@ -1031,7 +1043,7 @@ do ac_useropt=`expr "x$ac_option" : 'x-*without-\(.*\)'` # Reject names that are not valid shell variable names. expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null && - as_fn_error "invalid package name: $ac_useropt" + as_fn_error $? "invalid package name: $ac_useropt" ac_useropt_orig=$ac_useropt ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'` case $ac_user_opts in @@ -1061,8 +1073,8 @@ do | --x-librar=* | --x-libra=* | --x-libr=* | --x-lib=* | --x-li=* | --x-l=*) x_libraries=$ac_optarg ;; - -*) as_fn_error "unrecognized option: \`$ac_option' -Try \`$0 --help' for more information." + -*) as_fn_error $? "unrecognized option: \`$ac_option' +Try \`$0 --help' for more information" ;; *=*) @@ -1070,7 +1082,7 @@ Try \`$0 --help' for more information." # Reject names that are not valid shell variable names. case $ac_envvar in #( '' | [0-9]* | *[!_$as_cr_alnum]* ) - as_fn_error "invalid variable name: \`$ac_envvar'" ;; + as_fn_error $? "invalid variable name: \`$ac_envvar'" ;; esac eval $ac_envvar=\$ac_optarg export $ac_envvar ;; @@ -1080,7 +1092,7 @@ Try \`$0 --help' for more information." $as_echo "$as_me: WARNING: you should use --build, --host, --target" >&2 expr "x$ac_option" : ".*[^-._$as_cr_alnum]" >/dev/null && $as_echo "$as_me: WARNING: invalid host type: $ac_option" >&2 - : ${build_alias=$ac_option} ${host_alias=$ac_option} ${target_alias=$ac_option} + : "${build_alias=$ac_option} ${host_alias=$ac_option} ${target_alias=$ac_option}" ;; esac @@ -1088,13 +1100,13 @@ done if test -n "$ac_prev"; then ac_option=--`echo $ac_prev | sed 's/_/-/g'` - as_fn_error "missing argument to $ac_option" + as_fn_error $? "missing argument to $ac_option" fi if test -n "$ac_unrecognized_opts"; then case $enable_option_checking in no) ;; - fatal) as_fn_error "unrecognized options: $ac_unrecognized_opts" ;; + fatal) as_fn_error $? "unrecognized options: $ac_unrecognized_opts" ;; *) $as_echo "$as_me: WARNING: unrecognized options: $ac_unrecognized_opts" >&2 ;; esac fi @@ -1117,7 +1129,7 @@ do [\\/$]* | ?:[\\/]* ) continue;; NONE | '' ) case $ac_var in *prefix ) continue;; esac;; esac - as_fn_error "expected an absolute directory name for --$ac_var: $ac_val" + as_fn_error $? "expected an absolute directory name for --$ac_var: $ac_val" done # There might be people who depend on the old broken behavior: `$host' @@ -1131,8 +1143,8 @@ target=$target_alias if test "x$host_alias" != x; then if test "x$build_alias" = x; then cross_compiling=maybe - $as_echo "$as_me: WARNING: If you wanted to set the --build type, don't use --host. - If a cross compiler is detected then cross compile mode will be used." >&2 + $as_echo "$as_me: WARNING: if you wanted to set the --build type, don't use --host. + If a cross compiler is detected then cross compile mode will be used" >&2 elif test "x$build_alias" != "x$host_alias"; then cross_compiling=yes fi @@ -1147,9 +1159,9 @@ test "$silent" = yes && exec 6>/dev/null ac_pwd=`pwd` && test -n "$ac_pwd" && ac_ls_di=`ls -di .` && ac_pwd_ls_di=`cd "$ac_pwd" && ls -di .` || - as_fn_error "working directory cannot be determined" + as_fn_error $? "working directory cannot be determined" test "X$ac_ls_di" = "X$ac_pwd_ls_di" || - as_fn_error "pwd does not report name of working directory" + as_fn_error $? "pwd does not report name of working directory" # Find the source files, if location was not specified. @@ -1188,11 +1200,11 @@ else fi if test ! -r "$srcdir/$ac_unique_file"; then test "$ac_srcdir_defaulted" = yes && srcdir="$ac_confdir or .." - as_fn_error "cannot find sources ($ac_unique_file) in $srcdir" + as_fn_error $? "cannot find sources ($ac_unique_file) in $srcdir" fi ac_msg="sources are in $srcdir, but \`cd $srcdir' does not work" ac_abs_confdir=`( - cd "$srcdir" && test -r "./$ac_unique_file" || as_fn_error "$ac_msg" + cd "$srcdir" && test -r "./$ac_unique_file" || as_fn_error $? "$ac_msg" pwd)` # When building in place, set srcdir=. if test "$ac_abs_confdir" = "$ac_pwd"; then @@ -1232,7 +1244,7 @@ Configuration: --help=short display options specific to this package --help=recursive display the short help of all the included packages -V, --version display version information and exit - -q, --quiet, --silent do not print \`checking...' messages + -q, --quiet, --silent do not print \`checking ...' messages --cache-file=FILE cache test results in FILE [disabled] -C, --config-cache alias for \`--cache-file=config.cache' -n, --no-create do not create output files @@ -1378,9 +1390,9 @@ test -n "$ac_init_help" && exit $ac_status if $ac_init_version; then cat <<\_ACEOF jim configure 0.63 -generated by GNU Autoconf 2.65 +generated by GNU Autoconf 2.68 -Copyright (C) 2009 Free Software Foundation, Inc. +Copyright (C) 2010 Free Software Foundation, Inc. This configure script is free software; the Free Software Foundation gives unlimited permission to copy, distribute and modify it. _ACEOF @@ -1424,7 +1436,7 @@ sed 's/^/| /' conftest.$ac_ext >&5 ac_retval=1 fi - eval $as_lineno_stack; test "x$as_lineno_stack" = x && { as_lineno=; unset as_lineno;} + eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno as_fn_set_status $ac_retval } # ac_fn_c_try_compile @@ -1438,7 +1450,7 @@ ac_fn_c_check_type () as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5 $as_echo_n "checking for $2... " >&6; } -if { as_var=$3; eval "test \"\${$as_var+set}\" = set"; }; then : +if eval \${$3+:} false; then : $as_echo_n "(cached) " >&6 else eval "$3=no" @@ -1479,7 +1491,7 @@ fi eval ac_res=\$$3 { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5 $as_echo "$ac_res" >&6; } - eval $as_lineno_stack; test "x$as_lineno_stack" = x && { as_lineno=; unset as_lineno;} + eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno } # ac_fn_c_check_type @@ -1504,7 +1516,7 @@ $as_echo "$ac_try_echo"; } >&5 mv -f conftest.er1 conftest.err fi $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 - test $ac_status = 0; } >/dev/null && { + test $ac_status = 0; } > conftest.i && { test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || test ! -s conftest.err }; then : @@ -1515,7 +1527,7 @@ sed 's/^/| /' conftest.$ac_ext >&5 ac_retval=1 fi - eval $as_lineno_stack; test "x$as_lineno_stack" = x && { as_lineno=; unset as_lineno;} + eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno as_fn_set_status $ac_retval } # ac_fn_c_try_cpp @@ -1557,7 +1569,7 @@ sed 's/^/| /' conftest.$ac_ext >&5 ac_retval=$ac_status fi rm -rf conftest.dSYM conftest_ipa8_conftest.oo - eval $as_lineno_stack; test "x$as_lineno_stack" = x && { as_lineno=; unset as_lineno;} + eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno as_fn_set_status $ac_retval } # ac_fn_c_try_run @@ -1571,7 +1583,7 @@ ac_fn_c_check_header_compile () as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5 $as_echo_n "checking for $2... " >&6; } -if { as_var=$3; eval "test \"\${$as_var+set}\" = set"; }; then : +if eval \${$3+:} false; then : $as_echo_n "(cached) " >&6 else cat confdefs.h - <<_ACEOF >conftest.$ac_ext @@ -1589,7 +1601,7 @@ fi eval ac_res=\$$3 { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5 $as_echo "$ac_res" >&6; } - eval $as_lineno_stack; test "x$as_lineno_stack" = x && { as_lineno=; unset as_lineno;} + eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno } # ac_fn_c_check_header_compile @@ -1634,7 +1646,7 @@ fi # interfere with the next link command; also delete a directory that is # left behind by Apple's compiler. We do this before executing the actions. rm -rf conftest.dSYM conftest_ipa8_conftest.oo - eval $as_lineno_stack; test "x$as_lineno_stack" = x && { as_lineno=; unset as_lineno;} + eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno as_fn_set_status $ac_retval } # ac_fn_c_try_link @@ -1647,7 +1659,7 @@ ac_fn_c_check_func () as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5 $as_echo_n "checking for $2... " >&6; } -if { as_var=$3; eval "test \"\${$as_var+set}\" = set"; }; then : +if eval \${$3+:} false; then : $as_echo_n "(cached) " >&6 else cat confdefs.h - <<_ACEOF >conftest.$ac_ext @@ -1702,7 +1714,7 @@ fi eval ac_res=\$$3 { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5 $as_echo "$ac_res" >&6; } - eval $as_lineno_stack; test "x$as_lineno_stack" = x && { as_lineno=; unset as_lineno;} + eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno } # ac_fn_c_check_func cat >config.log <<_ACEOF @@ -1710,7 +1722,7 @@ This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by jim $as_me 0.63, which was -generated by GNU Autoconf 2.65. Invocation command line was +generated by GNU Autoconf 2.68. Invocation command line was $ $0 $@ @@ -1820,11 +1832,9 @@ trap 'exit_status=$? { echo - cat <<\_ASBOX -## ---------------- ## + $as_echo "## ---------------- ## ## Cache variables. ## -## ---------------- ## -_ASBOX +## ---------------- ##" echo # The following way of writing the cache mishandles newlines in values, ( @@ -1858,11 +1868,9 @@ $as_echo "$as_me: WARNING: cache variable $ac_var contains a newline" >&2;} ;; ) echo - cat <<\_ASBOX -## ----------------- ## + $as_echo "## ----------------- ## ## Output variables. ## -## ----------------- ## -_ASBOX +## ----------------- ##" echo for ac_var in $ac_subst_vars do @@ -1875,11 +1883,9 @@ _ASBOX echo if test -n "$ac_subst_files"; then - cat <<\_ASBOX -## ------------------- ## + $as_echo "## ------------------- ## ## File substitutions. ## -## ------------------- ## -_ASBOX +## ------------------- ##" echo for ac_var in $ac_subst_files do @@ -1893,11 +1899,9 @@ _ASBOX fi if test -s confdefs.h; then - cat <<\_ASBOX -## ----------- ## + $as_echo "## ----------- ## ## confdefs.h. ## -## ----------- ## -_ASBOX +## ----------- ##" echo cat confdefs.h echo @@ -1952,7 +1956,12 @@ _ACEOF ac_site_file1=NONE ac_site_file2=NONE if test -n "$CONFIG_SITE"; then - ac_site_file1=$CONFIG_SITE + # We do not want a PATH search for config.site. + case $CONFIG_SITE in #(( + -*) ac_site_file1=./$CONFIG_SITE;; + */*) ac_site_file1=$CONFIG_SITE;; + *) ac_site_file1=./$CONFIG_SITE;; + esac elif test "x$prefix" != xNONE; then ac_site_file1=$prefix/share/config.site ac_site_file2=$prefix/etc/config.site @@ -1967,7 +1976,11 @@ do { $as_echo "$as_me:${as_lineno-$LINENO}: loading site script $ac_site_file" >&5 $as_echo "$as_me: loading site script $ac_site_file" >&6;} sed 's/^/| /' "$ac_site_file" >&5 - . "$ac_site_file" + . "$ac_site_file" \ + || { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +as_fn_error $? "failed to load site script $ac_site_file +See \`config.log' for more details" "$LINENO" 5; } fi done @@ -2043,7 +2056,7 @@ if $ac_cache_corrupted; then $as_echo "$as_me: error: in \`$ac_pwd':" >&2;} { $as_echo "$as_me:${as_lineno-$LINENO}: error: changes in the environment can compromise the build" >&5 $as_echo "$as_me: error: changes in the environment can compromise the build" >&2;} - as_fn_error "run \`make distclean' and/or \`rm $cache_file' and start over" "$LINENO" 5 + as_fn_error $? "run \`make distclean' and/or \`rm $cache_file' and start over" "$LINENO" 5 fi ## -------------------- ## ## Main body of script. ## @@ -2056,7 +2069,7 @@ ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $ ac_compiler_gnu=$ac_cv_c_compiler_gnu -ac_config_headers="$ac_config_headers autoconf.h" +ac_config_headers="$ac_config_headers jimautoconf.h" # Checks for programs. @@ -2070,7 +2083,7 @@ if test -n "$ac_tool_prefix"; then set dummy ${ac_tool_prefix}gcc; ac_word=$2 { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 $as_echo_n "checking for $ac_word... " >&6; } -if test "${ac_cv_prog_CC+set}" = set; then : +if ${ac_cv_prog_CC+:} false; then : $as_echo_n "(cached) " >&6 else if test -n "$CC"; then @@ -2110,7 +2123,7 @@ if test -z "$ac_cv_prog_CC"; then set dummy gcc; ac_word=$2 { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 $as_echo_n "checking for $ac_word... " >&6; } -if test "${ac_cv_prog_ac_ct_CC+set}" = set; then : +if ${ac_cv_prog_ac_ct_CC+:} false; then : $as_echo_n "(cached) " >&6 else if test -n "$ac_ct_CC"; then @@ -2163,7 +2176,7 @@ if test -z "$CC"; then set dummy ${ac_tool_prefix}cc; ac_word=$2 { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 $as_echo_n "checking for $ac_word... " >&6; } -if test "${ac_cv_prog_CC+set}" = set; then : +if ${ac_cv_prog_CC+:} false; then : $as_echo_n "(cached) " >&6 else if test -n "$CC"; then @@ -2203,7 +2216,7 @@ if test -z "$CC"; then set dummy cc; ac_word=$2 { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 $as_echo_n "checking for $ac_word... " >&6; } -if test "${ac_cv_prog_CC+set}" = set; then : +if ${ac_cv_prog_CC+:} false; then : $as_echo_n "(cached) " >&6 else if test -n "$CC"; then @@ -2262,7 +2275,7 @@ if test -z "$CC"; then set dummy $ac_tool_prefix$ac_prog; ac_word=$2 { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 $as_echo_n "checking for $ac_word... " >&6; } -if test "${ac_cv_prog_CC+set}" = set; then : +if ${ac_cv_prog_CC+:} false; then : $as_echo_n "(cached) " >&6 else if test -n "$CC"; then @@ -2306,7 +2319,7 @@ do set dummy $ac_prog; ac_word=$2 { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 $as_echo_n "checking for $ac_word... " >&6; } -if test "${ac_cv_prog_ac_ct_CC+set}" = set; then : +if ${ac_cv_prog_ac_ct_CC+:} false; then : $as_echo_n "(cached) " >&6 else if test -n "$ac_ct_CC"; then @@ -2360,8 +2373,8 @@ fi test -z "$CC" && { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5 $as_echo "$as_me: error: in \`$ac_pwd':" >&2;} -as_fn_error "no acceptable C compiler found in \$PATH -See \`config.log' for more details." "$LINENO" 5; } +as_fn_error $? "no acceptable C compiler found in \$PATH +See \`config.log' for more details" "$LINENO" 5; } # Provide some information about the compiler. $as_echo "$as_me:${as_lineno-$LINENO}: checking for C compiler version" >&5 @@ -2475,9 +2488,8 @@ sed 's/^/| /' conftest.$ac_ext >&5 { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5 $as_echo "$as_me: error: in \`$ac_pwd':" >&2;} -{ as_fn_set_status 77 -as_fn_error "C compiler cannot create executables -See \`config.log' for more details." "$LINENO" 5; }; } +as_fn_error 77 "C compiler cannot create executables +See \`config.log' for more details" "$LINENO" 5; } else { $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5 $as_echo "yes" >&6; } @@ -2519,8 +2531,8 @@ done else { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5 $as_echo "$as_me: error: in \`$ac_pwd':" >&2;} -as_fn_error "cannot compute suffix of executables: cannot compile and link -See \`config.log' for more details." "$LINENO" 5; } +as_fn_error $? "cannot compute suffix of executables: cannot compile and link +See \`config.log' for more details" "$LINENO" 5; } fi rm -f conftest conftest$ac_cv_exeext { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_exeext" >&5 @@ -2577,9 +2589,9 @@ $as_echo "$ac_try_echo"; } >&5 else { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5 $as_echo "$as_me: error: in \`$ac_pwd':" >&2;} -as_fn_error "cannot run C compiled programs. +as_fn_error $? "cannot run C compiled programs. If you meant to cross compile, use \`--host'. -See \`config.log' for more details." "$LINENO" 5; } +See \`config.log' for more details" "$LINENO" 5; } fi fi fi @@ -2590,7 +2602,7 @@ rm -f conftest.$ac_ext conftest$ac_cv_exeext conftest.out ac_clean_files=$ac_clean_files_save { $as_echo "$as_me:${as_lineno-$LINENO}: checking for suffix of object files" >&5 $as_echo_n "checking for suffix of object files... " >&6; } -if test "${ac_cv_objext+set}" = set; then : +if ${ac_cv_objext+:} false; then : $as_echo_n "(cached) " >&6 else cat confdefs.h - <<_ACEOF >conftest.$ac_ext @@ -2630,8 +2642,8 @@ sed 's/^/| /' conftest.$ac_ext >&5 { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5 $as_echo "$as_me: error: in \`$ac_pwd':" >&2;} -as_fn_error "cannot compute suffix of object files: cannot compile -See \`config.log' for more details." "$LINENO" 5; } +as_fn_error $? "cannot compute suffix of object files: cannot compile +See \`config.log' for more details" "$LINENO" 5; } fi rm -f conftest.$ac_cv_objext conftest.$ac_ext fi @@ -2641,7 +2653,7 @@ OBJEXT=$ac_cv_objext ac_objext=$OBJEXT { $as_echo "$as_me:${as_lineno-$LINENO}: checking whether we are using the GNU C compiler" >&5 $as_echo_n "checking whether we are using the GNU C compiler... " >&6; } -if test "${ac_cv_c_compiler_gnu+set}" = set; then : +if ${ac_cv_c_compiler_gnu+:} false; then : $as_echo_n "(cached) " >&6 else cat confdefs.h - <<_ACEOF >conftest.$ac_ext @@ -2678,7 +2690,7 @@ ac_test_CFLAGS=${CFLAGS+set} ac_save_CFLAGS=$CFLAGS { $as_echo "$as_me:${as_lineno-$LINENO}: checking whether $CC accepts -g" >&5 $as_echo_n "checking whether $CC accepts -g... " >&6; } -if test "${ac_cv_prog_cc_g+set}" = set; then : +if ${ac_cv_prog_cc_g+:} false; then : $as_echo_n "(cached) " >&6 else ac_save_c_werror_flag=$ac_c_werror_flag @@ -2756,7 +2768,7 @@ else fi { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $CC option to accept ISO C89" >&5 $as_echo_n "checking for $CC option to accept ISO C89... " >&6; } -if test "${ac_cv_prog_cc_c89+set}" = set; then : +if ${ac_cv_prog_cc_c89+:} false; then : $as_echo_n "(cached) " >&6 else ac_cv_prog_cc_c89=no @@ -2855,7 +2867,7 @@ ac_compiler_gnu=$ac_cv_c_compiler_gnu $as_echo_n "checking whether ${MAKE-make} sets \$(MAKE)... " >&6; } set x ${MAKE-make} ac_make=`$as_echo "$2" | sed 's/+/p/g; s/[^a-zA-Z0-9_]/_/g'` -if { as_var=ac_cv_prog_make_${ac_make}_set; eval "test \"\${$as_var+set}\" = set"; }; then : +if eval \${ac_cv_prog_make_${ac_make}_set+:} false; then : $as_echo_n "(cached) " >&6 else cat >conftest.make <<\_ACEOF @@ -2863,7 +2875,7 @@ SHELL = /bin/sh all: @echo '@@@%%%=$(MAKE)=@@@%%%' _ACEOF -# GNU make sometimes prints "make[1]: Entering...", which would confuse us. +# GNU make sometimes prints "make[1]: Entering ...", which would confuse us. case `${MAKE-make} -f conftest.make 2>/dev/null` in *@@@%%%=?*=@@@%%%*) eval ac_cv_prog_make_${ac_make}_set=yes;; @@ -2897,7 +2909,7 @@ if test -n "$CPP" && test -d "$CPP"; then CPP= fi if test -z "$CPP"; then - if test "${ac_cv_prog_CPP+set}" = set; then : + if ${ac_cv_prog_CPP+:} false; then : $as_echo_n "(cached) " >&6 else # Double quotes because CPP needs to be expanded @@ -2927,7 +2939,7 @@ else # Broken: fails on valid input. continue fi -rm -f conftest.err conftest.$ac_ext +rm -f conftest.err conftest.i conftest.$ac_ext # OK, works on sane cases. Now check whether nonexistent headers # can be detected and how. @@ -2943,11 +2955,11 @@ else ac_preproc_ok=: break fi -rm -f conftest.err conftest.$ac_ext +rm -f conftest.err conftest.i conftest.$ac_ext done # Because of `break', _AC_PREPROC_IFELSE's cleaning code was skipped. -rm -f conftest.err conftest.$ac_ext +rm -f conftest.i conftest.err conftest.$ac_ext if $ac_preproc_ok; then : break fi @@ -2986,7 +2998,7 @@ else # Broken: fails on valid input. continue fi -rm -f conftest.err conftest.$ac_ext +rm -f conftest.err conftest.i conftest.$ac_ext # OK, works on sane cases. Now check whether nonexistent headers # can be detected and how. @@ -3002,18 +3014,18 @@ else ac_preproc_ok=: break fi -rm -f conftest.err conftest.$ac_ext +rm -f conftest.err conftest.i conftest.$ac_ext done # Because of `break', _AC_PREPROC_IFELSE's cleaning code was skipped. -rm -f conftest.err conftest.$ac_ext +rm -f conftest.i conftest.err conftest.$ac_ext if $ac_preproc_ok; then : else { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5 $as_echo "$as_me: error: in \`$ac_pwd':" >&2;} -as_fn_error "C preprocessor \"$CPP\" fails sanity check -See \`config.log' for more details." "$LINENO" 5; } +as_fn_error $? "C preprocessor \"$CPP\" fails sanity check +See \`config.log' for more details" "$LINENO" 5; } fi ac_ext=c @@ -3025,7 +3037,7 @@ ac_compiler_gnu=$ac_cv_c_compiler_gnu { $as_echo "$as_me:${as_lineno-$LINENO}: checking for grep that handles long lines and -e" >&5 $as_echo_n "checking for grep that handles long lines and -e... " >&6; } -if test "${ac_cv_path_GREP+set}" = set; then : +if ${ac_cv_path_GREP+:} false; then : $as_echo_n "(cached) " >&6 else if test -z "$GREP"; then @@ -3074,7 +3086,7 @@ esac done IFS=$as_save_IFS if test -z "$ac_cv_path_GREP"; then - as_fn_error "no acceptable grep could be found in $PATH$PATH_SEPARATOR/usr/xpg4/bin" "$LINENO" 5 + as_fn_error $? "no acceptable grep could be found in $PATH$PATH_SEPARATOR/usr/xpg4/bin" "$LINENO" 5 fi else ac_cv_path_GREP=$GREP @@ -3088,7 +3100,7 @@ $as_echo "$ac_cv_path_GREP" >&6; } { $as_echo "$as_me:${as_lineno-$LINENO}: checking for egrep" >&5 $as_echo_n "checking for egrep... " >&6; } -if test "${ac_cv_path_EGREP+set}" = set; then : +if ${ac_cv_path_EGREP+:} false; then : $as_echo_n "(cached) " >&6 else if echo a | $GREP -E '(a|b)' >/dev/null 2>&1 @@ -3140,7 +3152,7 @@ esac done IFS=$as_save_IFS if test -z "$ac_cv_path_EGREP"; then - as_fn_error "no acceptable egrep could be found in $PATH$PATH_SEPARATOR/usr/xpg4/bin" "$LINENO" 5 + as_fn_error $? "no acceptable egrep could be found in $PATH$PATH_SEPARATOR/usr/xpg4/bin" "$LINENO" 5 fi else ac_cv_path_EGREP=$EGREP @@ -3155,7 +3167,7 @@ $as_echo "$ac_cv_path_EGREP" >&6; } { $as_echo "$as_me:${as_lineno-$LINENO}: checking for ANSI C header files" >&5 $as_echo_n "checking for ANSI C header files... " >&6; } -if test "${ac_cv_header_stdc+set}" = set; then : +if ${ac_cv_header_stdc+:} false; then : $as_echo_n "(cached) " >&6 else cat confdefs.h - <<_ACEOF >conftest.$ac_ext @@ -3272,8 +3284,7 @@ do : as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh` ac_fn_c_check_header_compile "$LINENO" "$ac_header" "$as_ac_Header" "$ac_includes_default " -eval as_val=\$$as_ac_Header - if test "x$as_val" = x""yes; then : +if eval test \"x\$"$as_ac_Header"\" = x"yes"; then : cat >>confdefs.h <<_ACEOF #define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1 _ACEOF @@ -3284,12 +3295,16 @@ done ac_fn_c_check_type "$LINENO" "long long" "ac_cv_type_long_long" "$ac_includes_default" -if test "x$ac_cv_type_long_long" = x""yes; then : +if test "x$ac_cv_type_long_long" = xyes; then : cat >>confdefs.h <<_ACEOF #define HAVE_LONG_LONG 1 _ACEOF +DEFINE_HAVE_LONG_LONG="#define HAVE_LONG_LONG 1" + +else + DEFINE_HAVE_LONG_LONG="#undef HAVE_LONG_LONG" fi @@ -3297,16 +3312,22 @@ fi # Shared library support. Because we don't believe in automake! ac_aux_dir= for ac_dir in "$srcdir" "$srcdir/.." "$srcdir/../.."; do - for ac_t in install-sh install.sh shtool; do - if test -f "$ac_dir/$ac_t"; then - ac_aux_dir=$ac_dir - ac_install_sh="$ac_aux_dir/$ac_t -c" - break 2 - fi - done + if test -f "$ac_dir/install-sh"; then + ac_aux_dir=$ac_dir + ac_install_sh="$ac_aux_dir/install-sh -c" + break + elif test -f "$ac_dir/install.sh"; then + ac_aux_dir=$ac_dir + ac_install_sh="$ac_aux_dir/install.sh -c" + break + elif test -f "$ac_dir/shtool"; then + ac_aux_dir=$ac_dir + ac_install_sh="$ac_aux_dir/shtool install -c" + break + fi done if test -z "$ac_aux_dir"; then - as_fn_error "cannot find install-sh, install.sh, or shtool in \"$srcdir\" \"$srcdir/..\" \"$srcdir/../..\"" "$LINENO" 5 + as_fn_error $? "cannot find install-sh, install.sh, or shtool in \"$srcdir\" \"$srcdir/..\" \"$srcdir/../..\"" "$LINENO" 5 fi # These three variables are undocumented and unsupported, @@ -3320,27 +3341,27 @@ ac_configure="$SHELL $ac_aux_dir/configure" # Please don't use this var. # Make sure we can run config.sub. $SHELL "$ac_aux_dir/config.sub" sun4 >/dev/null 2>&1 || - as_fn_error "cannot run $SHELL $ac_aux_dir/config.sub" "$LINENO" 5 + as_fn_error $? "cannot run $SHELL $ac_aux_dir/config.sub" "$LINENO" 5 { $as_echo "$as_me:${as_lineno-$LINENO}: checking build system type" >&5 $as_echo_n "checking build system type... " >&6; } -if test "${ac_cv_build+set}" = set; then : +if ${ac_cv_build+:} false; then : $as_echo_n "(cached) " >&6 else ac_build_alias=$build_alias test "x$ac_build_alias" = x && ac_build_alias=`$SHELL "$ac_aux_dir/config.guess"` test "x$ac_build_alias" = x && - as_fn_error "cannot guess build type; you must specify one" "$LINENO" 5 + as_fn_error $? "cannot guess build type; you must specify one" "$LINENO" 5 ac_cv_build=`$SHELL "$ac_aux_dir/config.sub" $ac_build_alias` || - as_fn_error "$SHELL $ac_aux_dir/config.sub $ac_build_alias failed" "$LINENO" 5 + as_fn_error $? "$SHELL $ac_aux_dir/config.sub $ac_build_alias failed" "$LINENO" 5 fi { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_build" >&5 $as_echo "$ac_cv_build" >&6; } case $ac_cv_build in *-*-*) ;; -*) as_fn_error "invalid value of canonical build" "$LINENO" 5;; +*) as_fn_error $? "invalid value of canonical build" "$LINENO" 5;; esac build=$ac_cv_build ac_save_IFS=$IFS; IFS='-' @@ -3358,14 +3379,14 @@ case $build_os in *\ *) build_os=`echo "$build_os" | sed 's/ /-/g'`;; esac { $as_echo "$as_me:${as_lineno-$LINENO}: checking host system type" >&5 $as_echo_n "checking host system type... " >&6; } -if test "${ac_cv_host+set}" = set; then : +if ${ac_cv_host+:} false; then : $as_echo_n "(cached) " >&6 else if test "x$host_alias" = x; then ac_cv_host=$ac_cv_build else ac_cv_host=`$SHELL "$ac_aux_dir/config.sub" $host_alias` || - as_fn_error "$SHELL $ac_aux_dir/config.sub $host_alias failed" "$LINENO" 5 + as_fn_error $? "$SHELL $ac_aux_dir/config.sub $host_alias failed" "$LINENO" 5 fi fi @@ -3373,7 +3394,7 @@ fi $as_echo "$ac_cv_host" >&6; } case $ac_cv_host in *-*-*) ;; -*) as_fn_error "invalid value of canonical host" "$LINENO" 5;; +*) as_fn_error $? "invalid value of canonical host" "$LINENO" 5;; esac host=$ac_cv_host ac_save_IFS=$IFS; IFS='-' @@ -3402,6 +3423,11 @@ case $host in ;; esac +if test -n "$host_alias"; then + CROSS=$host_alias- + +fi + # Check whether --enable-fork was given. if test "${enable_fork+set}" = set; then : enableval=$enable_fork; @@ -3475,8 +3501,7 @@ for ac_func in ualarm sysinfo lstat fork vfork do : as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` ac_fn_c_check_func "$LINENO" "$ac_func" "$as_ac_var" -eval as_val=\$$as_ac_var - if test "x$as_val" = x""yes; then : +if eval test \"x\$"$as_ac_var"\" = x"yes"; then : cat >>confdefs.h <<_ACEOF #define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF @@ -3488,8 +3513,7 @@ for ac_func in backtrace geteuid mkstemp realpath strptime do : as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` ac_fn_c_check_func "$LINENO" "$ac_func" "$as_ac_var" -eval as_val=\$$as_ac_var - if test "x$as_val" = x""yes; then : +if eval test \"x\$"$as_ac_var"\" = x"yes"; then : cat >>confdefs.h <<_ACEOF #define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF @@ -3501,8 +3525,7 @@ for ac_func in regcomp waitpid sigaction sys_signame sys_siglist do : as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` ac_fn_c_check_func "$LINENO" "$ac_func" "$as_ac_var" -eval as_val=\$$as_ac_var - if test "x$as_val" = x""yes; then : +if eval test \"x\$"$as_ac_var"\" = x"yes"; then : cat >>confdefs.h <<_ACEOF #define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 _ACEOF @@ -3518,7 +3541,7 @@ SRCDIR=`dirname $0` { $as_echo "$as_me:${as_lineno-$LINENO}: checking for library containing dlopen" >&5 $as_echo_n "checking for library containing dlopen... " >&6; } -if test "${ac_cv_search_dlopen+set}" = set; then : +if ${ac_cv_search_dlopen+:} false; then : $as_echo_n "(cached) " >&6 else ac_func_search_save_LIBS=$LIBS @@ -3552,11 +3575,11 @@ for ac_lib in '' dl; do fi rm -f core conftest.err conftest.$ac_objext \ conftest$ac_exeext - if test "${ac_cv_search_dlopen+set}" = set; then : + if ${ac_cv_search_dlopen+:} false; then : break fi done -if test "${ac_cv_search_dlopen+set}" = set; then : +if ${ac_cv_search_dlopen+:} false; then : else ac_cv_search_dlopen=no @@ -3578,7 +3601,84 @@ $as_echo "#define HAVE_DLOPEN 1" >>confdefs.h fi -ac_config_files="$ac_config_files Makefile" +# Now that we know what the platform supports: + +# For all known extensions: +# - If it is disabled, remove it +# - Otherwise, check to see if it's pre-requisites are met +# - If yes, add it if it is enabled or is a default +# - If no, error if it is enabled, or do nothing otherwise + +needs_regexp="ac_cv_func_regcomp" +needs_syslog="ac_cv_func_syslog" +needs_exec="ac_cv_func_vfork" +needs_posix="ac_cv_func_waitpid" +needs_load="ac_cv_search_dlopen" +needs_signal="ac_cv_func_sigaction" +needs_readdir="ac_cv_func_opendir" + +ext_add=$(echo $with_jim_ext | tr ' ' '\n') +ext_del=$(echo $with_out_jim_ext | tr ' ' '\n') +for i in $ext_all; do + { $as_echo "$as_me:${as_lineno-$LINENO}: checking extension $i" >&5 +$as_echo_n "checking extension $i... " >&6; } + echo "$ext_del" | grep "^$i\$" >/dev/null + if test $? -eq 0; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: disabled" >&5 +$as_echo "disabled" >&6; } + continue + fi + # Check dependencies + eval "dep=\$needs_$i" + met=1 + for d in $dep; do + eval "check=\$$d" + if test "$check" == "no" -o -z "$check" ; then + met=0 + break + fi + done + echo "$ext_add" | grep "^$i\$" >/dev/null + if test $? -eq 0; then + if test $met -eq 0; then + as_fn_error $? "dependencies not met" "$LINENO" 5 + fi + { $as_echo "$as_me:${as_lineno-$LINENO}: result: enabled" >&5 +$as_echo "enabled" >&6; } + ext="$ext $i" + continue + fi + echo "$ext_default" | grep "^$i\$" >/dev/null + if test $? -eq 0; then + if test $met -eq 0; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: disabled (dependencies)" >&5 +$as_echo "disabled (dependencies)" >&6; } + continue + fi + { $as_echo "$as_me:${as_lineno-$LINENO}: result: enabled (default)" >&5 +$as_echo "enabled (default)" >&6; } + ext="$ext $i" + continue + fi + { $as_echo "$as_me:${as_lineno-$LINENO}: result: not enabled" >&5 +$as_echo "not enabled" >&6; } +done + +ext=$(echo $ext | tr '\n' ' ') +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: Jim extensions: $ext" >&5 +$as_echo "Jim extensions: $ext" >&6; } +JIM_EXTENSIONS=$ext + +for i in $ext; do + EXTRA_CFLAGS="$EXTRA_CFLAGS -Djim_ext_$i" +done + +EXTRA_CFLAGS=$EXTRA_CFLAGS + +SRCDIR=`dirname $0` + + +ac_config_files="$ac_config_files Makefile jimautoconfext.h" cat >confcache <<\_ACEOF # This file is a shell script that caches the results of configure @@ -3644,10 +3744,21 @@ $as_echo "$as_me: WARNING: cache variable $ac_var contains a newline" >&2;} ;; :end' >>confcache if diff "$cache_file" confcache >/dev/null 2>&1; then :; else if test -w "$cache_file"; then - test "x$cache_file" != "x/dev/null" && + if test "x$cache_file" != "x/dev/null"; then { $as_echo "$as_me:${as_lineno-$LINENO}: updating cache $cache_file" >&5 $as_echo "$as_me: updating cache $cache_file" >&6;} - cat confcache >$cache_file + if test ! -f "$cache_file" || test -h "$cache_file"; then + cat confcache >"$cache_file" + else + case $cache_file in #( + */* | ?:*) + mv -f confcache "$cache_file"$$ && + mv -f "$cache_file"$$ "$cache_file" ;; #( + *) + mv -f confcache "$cache_file" ;; + esac + fi + fi else { $as_echo "$as_me:${as_lineno-$LINENO}: not updating unwritable cache $cache_file" >&5 $as_echo "$as_me: not updating unwritable cache $cache_file" >&6;} @@ -3663,6 +3774,7 @@ DEFS=-DHAVE_CONFIG_H ac_libobjs= ac_ltlibobjs= +U= for ac_i in : $LIBOBJS; do test "x$ac_i" = x: && continue # 1. Remove the extension, and $U if already installed. ac_script='s/\$U\././;s/\.o$//;s/\.obj$//' @@ -3678,7 +3790,7 @@ LTLIBOBJS=$ac_ltlibobjs -: ${CONFIG_STATUS=./config.status} +: "${CONFIG_STATUS=./config.status}" ac_write_fail=0 ac_clean_files_save=$ac_clean_files ac_clean_files="$ac_clean_files $CONFIG_STATUS" @@ -3779,6 +3891,7 @@ fi IFS=" "" $as_nl" # Find who we are. Look in the path if we contain no directory separator. +as_myself= case $0 in #(( *[\\/]* ) as_myself=$0 ;; *) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR @@ -3824,19 +3937,19 @@ export LANGUAGE (unset CDPATH) >/dev/null 2>&1 && unset CDPATH -# as_fn_error ERROR [LINENO LOG_FD] -# --------------------------------- +# as_fn_error STATUS ERROR [LINENO LOG_FD] +# ---------------------------------------- # Output "`basename $0`: error: ERROR" to stderr. If LINENO and LOG_FD are # provided, also output the error to LOG_FD, referencing LINENO. Then exit the -# script with status $?, using 1 if that was 0. +# script with STATUS, using 1 if that was 0. as_fn_error () { - as_status=$?; test $as_status -eq 0 && as_status=1 - if test "$3"; then - as_lineno=${as_lineno-"$2"} as_lineno_stack=as_lineno_stack=$as_lineno_stack - $as_echo "$as_me:${as_lineno-$LINENO}: error: $1" >&$3 + as_status=$1; test $as_status -eq 0 && as_status=1 + if test "$4"; then + as_lineno=${as_lineno-"$3"} as_lineno_stack=as_lineno_stack=$as_lineno_stack + $as_echo "$as_me:${as_lineno-$LINENO}: error: $2" >&$4 fi - $as_echo "$as_me: error: $1" >&2 + $as_echo "$as_me: error: $2" >&2 as_fn_exit $as_status } # as_fn_error @@ -4032,7 +4145,7 @@ $as_echo X"$as_dir" | test -d "$as_dir" && break done test -z "$as_dirs" || eval "mkdir $as_dirs" - } || test -d "$as_dir" || as_fn_error "cannot create directory $as_dir" + } || test -d "$as_dir" || as_fn_error $? "cannot create directory $as_dir" } # as_fn_mkdir_p @@ -4086,7 +4199,7 @@ cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 # values after options handling. ac_log=" This file was extended by jim $as_me 0.63, which was -generated by GNU Autoconf 2.65. Invocation command line was +generated by GNU Autoconf 2.68. Invocation command line was CONFIG_FILES = $CONFIG_FILES CONFIG_HEADERS = $CONFIG_HEADERS @@ -4148,10 +4261,10 @@ cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 ac_cs_config="`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`" ac_cs_version="\\ jim config.status 0.63 -configured by $0, generated by GNU Autoconf 2.65, +configured by $0, generated by GNU Autoconf 2.68, with options \\"\$ac_cs_config\\" -Copyright (C) 2009 Free Software Foundation, Inc. +Copyright (C) 2010 Free Software Foundation, Inc. This config.status script is free software; the Free Software Foundation gives unlimited permission to copy, distribute and modify it." @@ -4166,11 +4279,16 @@ ac_need_defaults=: while test $# != 0 do case $1 in - --*=*) + --*=?*) ac_option=`expr "X$1" : 'X\([^=]*\)='` ac_optarg=`expr "X$1" : 'X[^=]*=\(.*\)'` ac_shift=: ;; + --*=) + ac_option=`expr "X$1" : 'X\([^=]*\)='` + ac_optarg= + ac_shift=: + ;; *) ac_option=$1 ac_optarg=$2 @@ -4192,6 +4310,7 @@ do $ac_shift case $ac_optarg in *\'*) ac_optarg=`$as_echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"` ;; + '') as_fn_error $? "missing file argument" ;; esac as_fn_append CONFIG_FILES " '$ac_optarg'" ac_need_defaults=false;; @@ -4204,7 +4323,7 @@ do ac_need_defaults=false;; --he | --h) # Conflict between --help and --header - as_fn_error "ambiguous option: \`$1' + as_fn_error $? "ambiguous option: \`$1' Try \`$0 --help' for more information.";; --help | --hel | -h ) $as_echo "$ac_cs_usage"; exit ;; @@ -4213,7 +4332,7 @@ Try \`$0 --help' for more information.";; ac_cs_silent=: ;; # This is an error. - -*) as_fn_error "unrecognized option: \`$1' + -*) as_fn_error $? "unrecognized option: \`$1' Try \`$0 --help' for more information." ;; *) as_fn_append ac_config_targets " $1" @@ -4262,10 +4381,11 @@ cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 for ac_config_target in $ac_config_targets do case $ac_config_target in - "autoconf.h") CONFIG_HEADERS="$CONFIG_HEADERS autoconf.h" ;; + "jimautoconf.h") CONFIG_HEADERS="$CONFIG_HEADERS jimautoconf.h" ;; "Makefile") CONFIG_FILES="$CONFIG_FILES Makefile" ;; + "jimautoconfext.h") CONFIG_FILES="$CONFIG_FILES jimautoconfext.h" ;; - *) as_fn_error "invalid argument: \`$ac_config_target'" "$LINENO" 5;; + *) as_fn_error $? "invalid argument: \`$ac_config_target'" "$LINENO" 5;; esac done @@ -4287,9 +4407,10 @@ fi # after its creation but before its name has been assigned to `$tmp'. $debug || { - tmp= + tmp= ac_tmp= trap 'exit_status=$? - { test -z "$tmp" || test ! -d "$tmp" || rm -fr "$tmp"; } && exit $exit_status + : "${ac_tmp:=$tmp}" + { test ! -d "$ac_tmp" || rm -fr "$ac_tmp"; } && exit $exit_status ' 0 trap 'as_fn_exit 1' 1 2 13 15 } @@ -4297,12 +4418,13 @@ $debug || { tmp=`(umask 077 && mktemp -d "./confXXXXXX") 2>/dev/null` && - test -n "$tmp" && test -d "$tmp" + test -d "$tmp" } || { tmp=./conf$$-$RANDOM (umask 077 && mkdir "$tmp") -} || as_fn_error "cannot create a temporary directory in ." "$LINENO" 5 +} || as_fn_error $? "cannot create a temporary directory in ." "$LINENO" 5 +ac_tmp=$tmp # Set up the scripts for CONFIG_FILES section. # No need to generate them if there are no CONFIG_FILES. @@ -4319,12 +4441,12 @@ if test "x$ac_cr" = x; then fi ac_cs_awk_cr=`$AWK 'BEGIN { print "a\rb" }' </dev/null 2>/dev/null` if test "$ac_cs_awk_cr" = "a${ac_cr}b"; then - ac_cs_awk_cr='\r' + ac_cs_awk_cr='\\r' else ac_cs_awk_cr=$ac_cr fi -echo 'BEGIN {' >"$tmp/subs1.awk" && +echo 'BEGIN {' >"$ac_tmp/subs1.awk" && _ACEOF @@ -4333,18 +4455,18 @@ _ACEOF echo "$ac_subst_vars" | sed 's/.*/&!$&$ac_delim/' && echo "_ACEOF" } >conf$$subs.sh || - as_fn_error "could not make $CONFIG_STATUS" "$LINENO" 5 -ac_delim_num=`echo "$ac_subst_vars" | grep -c '$'` + as_fn_error $? "could not make $CONFIG_STATUS" "$LINENO" 5 +ac_delim_num=`echo "$ac_subst_vars" | grep -c '^'` ac_delim='%!_!# ' for ac_last_try in false false false false false :; do . ./conf$$subs.sh || - as_fn_error "could not make $CONFIG_STATUS" "$LINENO" 5 + as_fn_error $? "could not make $CONFIG_STATUS" "$LINENO" 5 ac_delim_n=`sed -n "s/.*$ac_delim\$/X/p" conf$$subs.awk | grep -c X` if test $ac_delim_n = $ac_delim_num; then break elif $ac_last_try; then - as_fn_error "could not make $CONFIG_STATUS" "$LINENO" 5 + as_fn_error $? "could not make $CONFIG_STATUS" "$LINENO" 5 else ac_delim="$ac_delim!$ac_delim _$ac_delim!! " fi @@ -4352,7 +4474,7 @@ done rm -f conf$$subs.sh cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 -cat >>"\$tmp/subs1.awk" <<\\_ACAWK && +cat >>"\$ac_tmp/subs1.awk" <<\\_ACAWK && _ACEOF sed -n ' h @@ -4400,7 +4522,7 @@ t delim rm -f conf$$subs.awk cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 _ACAWK -cat >>"\$tmp/subs1.awk" <<_ACAWK && +cat >>"\$ac_tmp/subs1.awk" <<_ACAWK && for (key in S) S_is_set[key] = 1 FS = "" @@ -4432,21 +4554,29 @@ if sed "s/$ac_cr//" < /dev/null > /dev/null 2>&1; then sed "s/$ac_cr\$//; s/$ac_cr/$ac_cs_awk_cr/g" else cat -fi < "$tmp/subs1.awk" > "$tmp/subs.awk" \ - || as_fn_error "could not setup config files machinery" "$LINENO" 5 +fi < "$ac_tmp/subs1.awk" > "$ac_tmp/subs.awk" \ + || as_fn_error $? "could not setup config files machinery" "$LINENO" 5 _ACEOF -# VPATH may cause trouble with some makes, so we remove $(srcdir), -# ${srcdir} and @srcdir@ from VPATH if srcdir is ".", strip leading and +# VPATH may cause trouble with some makes, so we remove sole $(srcdir), +# ${srcdir} and @srcdir@ entries from VPATH if srcdir is ".", strip leading and # trailing colons and then remove the whole line if VPATH becomes empty # (actually we leave an empty line to preserve line numbers). if test "x$srcdir" = x.; then - ac_vpsub='/^[ ]*VPATH[ ]*=/{ -s/:*\$(srcdir):*/:/ -s/:*\${srcdir}:*/:/ -s/:*@srcdir@:*/:/ -s/^\([^=]*=[ ]*\):*/\1/ + ac_vpsub='/^[ ]*VPATH[ ]*=[ ]*/{ +h +s/// +s/^/:/ +s/[ ]*$/:/ +s/:\$(srcdir):/:/g +s/:\${srcdir}:/:/g +s/:@srcdir@:/:/g +s/^:*// s/:*$// +x +s/\(=[ ]*\).*/\1/ +G +s/\n// s/^[^=]*=[ ]*$// }' fi @@ -4458,7 +4588,7 @@ fi # test -n "$CONFIG_FILES" # No need to generate them if there are no CONFIG_HEADERS. # This happens for instance with `./config.status Makefile'. if test -n "$CONFIG_HEADERS"; then -cat >"$tmp/defines.awk" <<\_ACAWK || +cat >"$ac_tmp/defines.awk" <<\_ACAWK || BEGIN { _ACEOF @@ -4470,11 +4600,11 @@ _ACEOF # handling of long lines. ac_delim='%!_!# ' for ac_last_try in false false :; do - ac_t=`sed -n "/$ac_delim/p" confdefs.h` - if test -z "$ac_t"; then + ac_tt=`sed -n "/$ac_delim/p" confdefs.h` + if test -z "$ac_tt"; then break elif $ac_last_try; then - as_fn_error "could not make $CONFIG_HEADERS" "$LINENO" 5 + as_fn_error $? "could not make $CONFIG_HEADERS" "$LINENO" 5 else ac_delim="$ac_delim!$ac_delim _$ac_delim!! " fi @@ -4559,7 +4689,7 @@ cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 _ACAWK _ACEOF cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 - as_fn_error "could not setup config headers machinery" "$LINENO" 5 + as_fn_error $? "could not setup config headers machinery" "$LINENO" 5 fi # test -n "$CONFIG_HEADERS" @@ -4572,7 +4702,7 @@ do esac case $ac_mode$ac_tag in :[FHL]*:*);; - :L* | :C*:*) as_fn_error "invalid tag \`$ac_tag'" "$LINENO" 5;; + :L* | :C*:*) as_fn_error $? "invalid tag \`$ac_tag'" "$LINENO" 5;; :[FH]-) ac_tag=-:-;; :[FH]*) ac_tag=$ac_tag:$ac_tag.in;; esac @@ -4591,7 +4721,7 @@ do for ac_f do case $ac_f in - -) ac_f="$tmp/stdin";; + -) ac_f="$ac_tmp/stdin";; *) # Look for the file first in the build tree, then in the source tree # (if the path is not absolute). The absolute path cannot be DOS-style, # because $ac_f cannot contain `:'. @@ -4600,7 +4730,7 @@ do [\\/$]*) false;; *) test -f "$srcdir/$ac_f" && ac_f="$srcdir/$ac_f";; esac || - as_fn_error "cannot find input file: \`$ac_f'" "$LINENO" 5;; + as_fn_error 1 "cannot find input file: \`$ac_f'" "$LINENO" 5;; esac case $ac_f in *\'*) ac_f=`$as_echo "$ac_f" | sed "s/'/'\\\\\\\\''/g"`;; esac as_fn_append ac_file_inputs " '$ac_f'" @@ -4626,8 +4756,8 @@ $as_echo "$as_me: creating $ac_file" >&6;} esac case $ac_tag in - *:-:* | *:-) cat >"$tmp/stdin" \ - || as_fn_error "could not create $ac_file" "$LINENO" 5 ;; + *:-:* | *:-) cat >"$ac_tmp/stdin" \ + || as_fn_error $? "could not create $ac_file" "$LINENO" 5 ;; esac ;; esac @@ -4752,23 +4882,24 @@ s&@abs_builddir@&$ac_abs_builddir&;t t s&@abs_top_builddir@&$ac_abs_top_builddir&;t t $ac_datarootdir_hack " -eval sed \"\$ac_sed_extra\" "$ac_file_inputs" | $AWK -f "$tmp/subs.awk" >$tmp/out \ - || as_fn_error "could not create $ac_file" "$LINENO" 5 +eval sed \"\$ac_sed_extra\" "$ac_file_inputs" | $AWK -f "$ac_tmp/subs.awk" \ + >$ac_tmp/out || as_fn_error $? "could not create $ac_file" "$LINENO" 5 test -z "$ac_datarootdir_hack$ac_datarootdir_seen" && - { ac_out=`sed -n '/\${datarootdir}/p' "$tmp/out"`; test -n "$ac_out"; } && - { ac_out=`sed -n '/^[ ]*datarootdir[ ]*:*=/p' "$tmp/out"`; test -z "$ac_out"; } && + { ac_out=`sed -n '/\${datarootdir}/p' "$ac_tmp/out"`; test -n "$ac_out"; } && + { ac_out=`sed -n '/^[ ]*datarootdir[ ]*:*=/p' \ + "$ac_tmp/out"`; test -z "$ac_out"; } && { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $ac_file contains a reference to the variable \`datarootdir' -which seems to be undefined. Please make sure it is defined." >&5 +which seems to be undefined. Please make sure it is defined" >&5 $as_echo "$as_me: WARNING: $ac_file contains a reference to the variable \`datarootdir' -which seems to be undefined. Please make sure it is defined." >&2;} +which seems to be undefined. Please make sure it is defined" >&2;} - rm -f "$tmp/stdin" + rm -f "$ac_tmp/stdin" case $ac_file in - -) cat "$tmp/out" && rm -f "$tmp/out";; - *) rm -f "$ac_file" && mv "$tmp/out" "$ac_file";; + -) cat "$ac_tmp/out" && rm -f "$ac_tmp/out";; + *) rm -f "$ac_file" && mv "$ac_tmp/out" "$ac_file";; esac \ - || as_fn_error "could not create $ac_file" "$LINENO" 5 + || as_fn_error $? "could not create $ac_file" "$LINENO" 5 ;; :H) # @@ -4777,21 +4908,21 @@ which seems to be undefined. Please make sure it is defined." >&2;} if test x"$ac_file" != x-; then { $as_echo "/* $configure_input */" \ - && eval '$AWK -f "$tmp/defines.awk"' "$ac_file_inputs" - } >"$tmp/config.h" \ - || as_fn_error "could not create $ac_file" "$LINENO" 5 - if diff "$ac_file" "$tmp/config.h" >/dev/null 2>&1; then + && eval '$AWK -f "$ac_tmp/defines.awk"' "$ac_file_inputs" + } >"$ac_tmp/config.h" \ + || as_fn_error $? "could not create $ac_file" "$LINENO" 5 + if diff "$ac_file" "$ac_tmp/config.h" >/dev/null 2>&1; then { $as_echo "$as_me:${as_lineno-$LINENO}: $ac_file is unchanged" >&5 $as_echo "$as_me: $ac_file is unchanged" >&6;} else rm -f "$ac_file" - mv "$tmp/config.h" "$ac_file" \ - || as_fn_error "could not create $ac_file" "$LINENO" 5 + mv "$ac_tmp/config.h" "$ac_file" \ + || as_fn_error $? "could not create $ac_file" "$LINENO" 5 fi else $as_echo "/* $configure_input */" \ - && eval '$AWK -f "$tmp/defines.awk"' "$ac_file_inputs" \ - || as_fn_error "could not create -" "$LINENO" 5 + && eval '$AWK -f "$ac_tmp/defines.awk"' "$ac_file_inputs" \ + || as_fn_error $? "could not create -" "$LINENO" 5 fi ;; @@ -4806,7 +4937,7 @@ _ACEOF ac_clean_files=$ac_clean_files_save test $ac_write_fail = 0 || - as_fn_error "write failure creating $CONFIG_STATUS" "$LINENO" 5 + as_fn_error $? "write failure creating $CONFIG_STATUS" "$LINENO" 5 # configure is writing to config.log, and then calls config.status. @@ -4827,7 +4958,7 @@ if test "$no_create" != yes; then exec 5>>config.log # Use ||, not &&, to avoid exiting from the if with $? = 1, which # would make configure fail if this is the last instruction. - $ac_cs_success || as_fn_exit $? + $ac_cs_success || as_fn_exit 1 fi if test -n "$ac_unrecognized_opts" && test "$enable_option_checking" != no; then { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: unrecognized options: $ac_unrecognized_opts" >&5 diff --git a/configure.ac b/configure.ac index ff7738a..052915d 100755 --- a/configure.ac +++ b/configure.ac @@ -3,14 +3,14 @@ AC_PREREQ(2.57) AC_INIT([jim], [0.63], [steveb@workware.net.au]) -AC_CONFIG_HEADER(autoconf.h) +AC_CONFIG_HEADER(jimautoconf.h) # Checks for programs. AC_PROG_CC AC_PROG_MAKE_SET # Checks for types -AC_CHECK_TYPES(long long) +AC_CHECK_TYPES(long long, AC_SUBST(DEFINE_HAVE_LONG_LONG,["#define HAVE_LONG_LONG 1"]),AC_SUBST(DEFINE_HAVE_LONG_LONG,["#undef HAVE_LONG_LONG"])) # Shared library support. Because we don't believe in automake! AC_CANONICAL_HOST @@ -23,6 +23,10 @@ case $host in AC_SUBST(SH_LDFLAGS,-shared);; esac +if test -n "$host_alias"; then + AC_SUBST(CROSS,$host_alias-) +fi + AC_ARG_ENABLE(fork, [ --disable-fork do not use fork (no exec, etc.)], [ @@ -89,5 +93,72 @@ AC_SEARCH_LIBS(dlopen, dl, AC_DEFINE([HAVE_DLOPEN],[1],[Have the dlopen function]) ) -AC_CONFIG_FILES([Makefile]) +# Now that we know what the platform supports: + +# For all known extensions: +# - If it is disabled, remove it +# - Otherwise, check to see if it's pre-requisites are met +# - If yes, add it if it is enabled or is a default +# - If no, error if it is enabled, or do nothing otherwise + +needs_regexp="ac_cv_func_regcomp" +needs_syslog="ac_cv_func_syslog" +needs_exec="ac_cv_func_vfork" +needs_posix="ac_cv_func_waitpid" +needs_load="ac_cv_search_dlopen" +needs_signal="ac_cv_func_sigaction" +needs_readdir="ac_cv_func_opendir" + +ext_add=$(echo $with_jim_ext | tr ' ' '\n') +ext_del=$(echo $with_out_jim_ext | tr ' ' '\n') +for i in $ext_all; do + AC_MSG_CHECKING(extension $i) + echo "$ext_del" | grep "^$i\$" >/dev/null + if test $? -eq 0; then + AC_MSG_RESULT(disabled) + continue + fi + # Check dependencies + eval "dep=\$needs_$i" + met=1 + for d in $dep; do + eval "check=\$$d" + if test "$check" == "no" -o -z "$check" ; then + met=0 + break + fi + done + echo "$ext_add" | grep "^$i\$" >/dev/null + if test $? -eq 0; then + if test $met -eq 0; then + AC_MSG_ERROR(dependencies not met) + fi + AC_MSG_RESULT(enabled) + ext="$ext $i" + continue + fi + echo "$ext_default" | grep "^$i\$" >/dev/null + if test $? -eq 0; then + if test $met -eq 0; then + AC_MSG_RESULT(disabled (dependencies)) + continue + fi + AC_MSG_RESULT(enabled (default)) + ext="$ext $i" + continue + fi + AC_MSG_RESULT(not enabled) +done + +ext=$(echo $ext | tr '\n' ' ') +AC_MSG_RESULT(Jim extensions: $ext) +AC_SUBST(JIM_EXTENSIONS,$ext) +for i in $ext; do + EXTRA_CFLAGS="$EXTRA_CFLAGS -Djim_ext_$i" +done + +AC_SUBST(EXTRA_CFLAGS,$EXTRA_CFLAGS) +AC_SUBST(SRCDIR,`dirname $0`) + +AC_CONFIG_FILES([Makefile jimautoconfext.h]) AC_OUTPUT @@ -90,7 +90,7 @@ extern "C" { #endif #ifndef HAVE_NO_AUTOCONF -#include <autoconf.h> +#include <jimautoconf.h> #endif #if defined(HAVE_DLOPEN) diff --git a/autoconf.h.in b/jimautoconf.h.in index 25edf2b..6c0772f 100644 --- a/autoconf.h.in +++ b/jimautoconf.h.in @@ -1,4 +1,4 @@ -/* autoconf.h.in. Generated from configure.ac by autoheader. */ +/* jimautoconf.h.in. Generated from configure.ac by autoheader. */ /* Define to 1 if you have the `backtrace' function. */ #undef HAVE_BACKTRACE diff --git a/jimautoconfext.h.in b/jimautoconfext.h.in new file mode 100644 index 0000000..2394bc5 --- /dev/null +++ b/jimautoconfext.h.in @@ -0,0 +1,2 @@ +/* Public autoconf settings */ +@DEFINE_HAVE_LONG_LONG@ |