summaryrefslogtreecommitdiffstats
path: root/doc/binary.n
diff options
context:
space:
mode:
authorjan.nijtmans <nijtmans@users.sourceforge.net>2020-11-19 08:57:49 (GMT)
committerjan.nijtmans <nijtmans@users.sourceforge.net>2020-11-19 08:57:49 (GMT)
commit14ec7c1d858d00e7c69c80c28cf599095dd3feaf (patch)
treec1bbe67b99dbfd4a521682975956b358f53f7bb2 /doc/binary.n
parent72c49f69099c98bd55334dbad3d68645c72bc707 (diff)
parent8e1f957a669b2f4b84dca7e8a27f2985c0625172 (diff)
downloadtcl-14ec7c1d858d00e7c69c80c28cf599095dd3feaf.zip
tcl-14ec7c1d858d00e7c69c80c28cf599095dd3feaf.tar.gz
tcl-14ec7c1d858d00e7c69c80c28cf599095dd3feaf.tar.bz2
Merge 8.7
Diffstat (limited to 'doc/binary.n')
-rw-r--r--doc/binary.n9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/binary.n b/doc/binary.n
index 0e8b28e..9b8b106 100644
--- a/doc/binary.n
+++ b/doc/binary.n
@@ -762,6 +762,15 @@ high-to-low order within each byte. For example,
will return \fB2\fR with \fB01110\fR stored in \fIvar1\fR and
\fB1000011100000101\fR stored in \fIvar2\fR.
.RE
+.IP \fBC\fR 5
+This form is similar to \fBA\fR, except that it scans the data from start
+and terminates at the first null (C string semantics). For example,
+.RS
+.CS
+\fBbinary scan\fR "abc\e000efghi" C* var1
+.CE
+will return \fB1\fR with \fBabc\fR stored in \fIvar1\fR.
+.RE
.IP \fBH\fR 5
The data is turned into a string of \fIcount\fR hexadecimal digits in
high-to-low order represented as a sequence of characters in the set