summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorjan.nijtmans <nijtmans@users.sourceforge.net>2024-02-01 09:42:36 (GMT)
committerjan.nijtmans <nijtmans@users.sourceforge.net>2024-02-01 09:42:36 (GMT)
commit28ad5a88c9d11e3f16a86474b0e82dd7d6bc9d37 (patch)
tree48b83eb87ffeaf245517c2823e6f358d4ec55721
parent19d9008e3156868770dc908cbd835e596dc744a5 (diff)
downloadtcl-28ad5a88c9d11e3f16a86474b0e82dd7d6bc9d37.zip
tcl-28ad5a88c9d11e3f16a86474b0e82dd7d6bc9d37.tar.gz
tcl-28ad5a88c9d11e3f16a86474b0e82dd7d6bc9d37.tar.bz2
Forgot that long doubles are supported in Tcl_ObjPrintf()
-rw-r--r--doc/StringObj.34
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/StringObj.3 b/doc/StringObj.3
index 65216d3..02fda8b 100644
--- a/doc/StringObj.3
+++ b/doc/StringObj.3
@@ -323,8 +323,8 @@ core formatting engine used by \fBTcl_Format\fR. This means the set of
supported conversion specifiers is that of the \fBformat\fR command but
the behavior is as similar as possible to \fBsprintf\fR. The "hh" and
(Microsoft-specific) "w" format specifiers are not supported. The "L"
-format specifier means that an "mp_int *" argument is expected (in combination
-with "d"/"i"/"u"/"o"/"x"/"X", it cannot be used for long doubles). When a
+format specifier means that an "mp_int *" argument is expected (or a
+"long double" in combination with \fB[aAeEgGaA]\fR). When a
conversion specifier passed to \fBTcl_ObjPrintf\fR includes a precision,
the value is taken as a number of bytes, as \fBsprintf\fR does, and not
as a number of characters, as \fBformat\fR does. This is done on the