summaryrefslogtreecommitdiffstats
path: root/doc/FindExec.3
diff options
context:
space:
mode:
Diffstat (limited to 'doc/FindExec.3')
-rw-r--r--doc/FindExec.37
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/FindExec.3 b/doc/FindExec.3
index af9d9ad..b01315c 100644
--- a/doc/FindExec.3
+++ b/doc/FindExec.3
@@ -45,6 +45,13 @@ application's executable, if possible. If it fails to find
the binary, then future calls to \fBinfo nameofexecutable\fR
will return an empty string.
.PP
+On Windows platforms this procedure is typically invoked as the very
+first thing in the application's main program as well; Its \fIargv[0]\fR
+argument is only used to indicate whether the executable has a stderr
+channel (any non-null value) or not (the value null). If \fBTcl_SetPanicProc\fR
+is never called and no debugger is running, this determines whether
+the panic message is sent to stderr or to a standard system dialog.
+.PP
\fBTcl_GetNameOfExecutable\fR simply returns a pointer to the
internal full path name of the executable file as computed by
\fBTcl_FindExecutable\fR. This procedure call is the C API