The C API , for example, assumes that the Tcl and C libraries are bound together in a single application, to be executed as a single process. My recent book has 100 pages. It was mangled. It should be For concurrent operations, both languages use open . There's one other serious typo.
Many languages also can open pipes.
There are a few differences between Unix shared objects and Windows DLLs, but the overall procedure is similar. For a dynamically loaded Tcl extension, you won't need the .LIB file. Also, if there is a long list of .OBJ files you may run into command-line length limitations. Command-line arguments and parameter files can be freely mixed on the command line.