.\" Copyright (c) 1980 The Regents of the University of California.
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the University of
.\" California, Berkeley and its contributors.
.\" 4. Neither the name of the University nor the names of its contributors
.\" may be used to endorse or promote products derived from this software
.\" without specific prior written permission.
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" @(#)xstr.1 6.4 (Berkeley) 4/24/91
.Nd "extract strings from C programs to implement shared 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, most useful if they
reads from the standard input.
will extract the strings from the C source
string references by expressions of the form (&xstr[number])
An appropriate declaration of
is prepended to the file.
The resulting C text is placed in the file
The strings from this file are placed in the
data base if they are not there already.
Repeated strings and strings which are suffices of existing strings
do not cause changes to the data base.
After all components of a large program have been compiled a file
space can be created by a command of the form
.Bd -literal -offset indent
should then be compiled and loaded with the rest
If possible, the array can be made read-only (shared) saving
can also be used on a single file.
.Bd -literal -offset indent
as before, without using or affecting any
file in the same directory.
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.
An appropriate command sequence for running
after the C preprocessor is:
.Bd -literal -offset indent -compact
cc \-E name.c | xstr \-c \-
unless new items are added, thus
.Bl -tag -width /tmp/xsxx* -compact
C source for definition of array `xstr'
Temp file when `xstr name' doesn't touch
If a string is a suffix of another string in the data base,
but the shorter string is seen first by
both strings will be placed in the data base, when just
placing the longer one there will do.