Tangling parts

If you construct your Interscript sources as a tree, using the "@include_file()" command, and you follow certain rules, you can run Interscript on the included file to extract the code, for just that file. The Interscript sources are constructed this way. This feature is vital for building big systems because it allows you to extract the code from files you have changed, without extracting code from those that have not.

You must ensure that code files are lexically contained entirely in a single include file. More generally, the include file does not rely on any context from its parent (except for that which is determined from the command line).

If you weave an include file, you will get a separate document for that include file which will, in general, not be linked to the master document: it will be in a separate file, named after the include file, and headings will be numbered separately.

[There is currently no simple way to require a separate source be built entirely independently so that the master document can link to it. This would be especially useful, because it would also permit time stamps to be checked and avoid unnecessary processing.]