xstr maintains a file called strings into which strings in component parts of a large program are hashed. These strings are replaced with references to this common
area. This serves to implement shared constant strings, which are most useful if they are also read-only.
The command:
|
example% xstr -c filename
|
extracts the strings from the C source in name, replacing string references by expressions of the form &xstr[number] for some number.
An appropriate declaration of xstr is prepended to the file. The resulting C text is placed in the file x.c, to then be compiled. The strings from this file are
placed in the strings data base if they are not there already. Repeated strings and strings which are suffixes of existing strings do not cause changes to the data base.
After all components of a large program have been compiled, a file declaring the common xstr space called xs.c can be created by a command of the form:
This xs.c file should then be compiled and loaded with the rest of the program. If possible, the array can be made read-only (shared) saving space and swap overhead.
xstr can also be used on a single file. A command:
example% xstr filename
creates files x.c and xs.c as before, without using or affecting any strings file in the same directory.
It may be useful to run xstr after the C preprocessor if any macro definitions yield strings or if there is conditional code which contains strings which may not, in fact, be needed. xstr reads from the standard input when the argument `-' is given. An appropriate command sequence for running xstr after the C preprocessor is:
|
example% cc -E name.c | xstr -c -
example% cc -c x.c
example% mv x.o name.o
|
xstr does not touch the file strings unless new items are added; thus make(1S) can avoid remaking xs.o unless truly necessary.
|