Merge 8.7, but update for TIP #476

1 files changed, 5 insertions, 2 deletions

diff --git a/doc/StringObj.3 b/doc/StringObj.3
index 6f2abff..65216d3 100644
--- a/doc/StringObj.3
+++ b/doc/StringObj.3
@@ -320,8 +320,11 @@ sprintf(buf, format, ...);
 but with greater convenience and no need to
 determine \fBSOME_SUITABLE_LENGTH\fR. The formatting is done with the same
 core formatting engine used by \fBTcl_Format\fR.  This means the set of
-supported conversion specifiers is that of the \fBformat\fR command and
-not that of the \fBsprintf\fR routine where the two sets differ. When a
+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
 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