char * Tcl_InitStubs(interp, version, exact)
- Tcl_Interp *interp (in)
Tcl interpreter handle.
- char *version (in)
A version string consisting of one or more decimal numbers separated by dots.
- int exact (in)
Non-zero means that only the particular version specified by version is acceptable. Zero means that versions newer than version are also acceptable as long as they have the same major version number as version.
The Tcl stubs mechanism defines a way to dynamically bind extensions to a particular Tcl implementation at run time. This provides two significant benefits to Tcl users:
Extensions that use the stubs mechanism can be loaded into multiple versions of Tcl without being recompiled or relinked.
Extensions that use the stubs mechanism can be dynamically loaded into statically-linked Tcl applications.
The stubs mechanism accomplishes this by exporting function tables that define an interface to the Tcl API. The extension then accesses the Tcl API through offsets into the function table, so there are no direct references to any of the Tcl library's symbols. This redirection is transparent to the extension, so an extension writer can continue to use all public Tcl functions as documented.
The stubs mechanism requires no changes to applications incorporating Tcl interpreters. Only developers creating C-based Tcl extensions need to take steps to use the stubs mechanism with their extensions.
Enabling the stubs mechanism for an extension requires the following steps:
Tcl_InitStubs()in the extension before calling any other Tcl functions.
Define the USE_TCL_STUBS symbol. Typically, you would include the -DUSE_TCL_STUBS flag when compiling the extension.
Link the extension with the Tcl stubs library instead of the standard Tcl library. On UNIX platforms, the library name is libtclstub8.1.a; on Windows platforms, the library name is tclstub81.lib.
If the extension also requires the Tk API, it must also call Tk_InitStubs to initialize the Tk stubs interface and link with the Tk stubs libraries. See the Tk_InitStubs page for more information.
Windows Server 2012. Windows 8.1. Windows Server 2012 R2. Windows 10. Windows Server 2016. Windows Server 2019.
PTC MKS Toolkit for Professional Developers
PTC MKS Toolkit for Enterprise Developers
PTC MKS Toolkit for Enterprise Developers 64-Bit Edition
PTC MKS Toolkit 10.3 Documentation Build 39.