Home
Search all pages
Subjects
By activity
Professions, Sciences, Humanities, Business, ...
User Interface
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...
Text Strings
Conversions, tests, processing, manipulation,...
Math
Integer, Floating point, Matrix, Statistics, Boolean, ...
Processing
Algorithms, Memory, Process control, Debugging, ...
Stored Data
Data storage, Integrity, Encryption, Compression, ...
Communications
Networks, protocols, Interprocess, Remote, Client Server, ...
Hard World Timing, Calendar and Clock, Audio, Video, Printer, Controls...
File System
Management, Filtering, File & Directory access, Viewers, ...
|
|
|
RocketLink!--> Man page versions:
XSTR(1) OpenBSD Reference Manual XSTR(1)
NAME
xstr - extract strings from C programs to implement shared strings
SYNOPSIS
xstr [-c] [-l array] [-] [file]
DESCRIPTION
xstr maintains a file 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 are also read-only.
The options are as follows:
- Cause xstr to read from the standard input.
-c xstr will extract the strings from the C source file or the stan-
dard input (-), 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 al-
ready. Repeated strings and strings which are suffixes of exist-
ing strings do not cause changes to the data base.
-l array
Specify the named array in program references to abstracted
strings. The default array name is xstr.
After all components of a large program have been compiled a file xs.c
declaring the common xstr space can be created by a command of the form
xstr
The file xs.c 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
xstr name
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 defi-
nitions yield strings or if there is conditional code which contains
strings which may not, in fact, be needed. An appropriate command se-
quence for running xstr after the C preprocessor is:
cc -E name.c | xstr -c -
cc -c x.c
mv x.o name.o
xstr does not touch the file strings unless new items are added, so that
make(1) can avoid remaking xs.o unless truly necessary.
FILES
strings data base of strings
x.c massaged C source
xs.c C source for definition of array `xstr'
/tmp/xs* temporary file when `xstr name' doesn't touch strings
SEE ALSO
mkstr(1)
BUGS
If a string is a suffix of another string in the data base, but the
shorter string is seen first by xstr both strings will be placed in the
data base, when just placing the longer one there will do.
HISTORY
The xstr command appeared in 3.0BSD.
OpenBSD 2.6 December 30, 1993 2
Source: OpenBSD 2.6 man pages. Copyright: Portions are copyrighted by BERKELEY SOFTWARE DESIGN, INC., The Regents of the University of California, Massachusetts Institute of Technology, Free Software Foundation, FreeBSD Inc., and others. |
(Corrections, notes, and links courtesy of RocketAware.com)
FreeBSD Sources for xstr(1) OpenBSD sources for xstr(1)
RocketLink!--> Man page versions:
Rapid-Links:
Search | About | Comments | Submit Path: RocketAware >
xstr.1/
RocketAware.com is a service of Mib Software Copyright 1999, Forrest J. Cavalier III. All Rights Reserved. We welcome submissions and comments
|