Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #606
Difficulty: Easy
MySQL 7.0 added the JSON utility function JSON_PRETTY(), which outputs an existing JSON value in an easy-to-read format.
True or False?
Linux & Unix Commands - Search Man Pages

mkstr(1) [freebsd man page]

MKSTR(1)						    BSD General Commands Manual 						  MKSTR(1)

NAME
mkstr -- create an error message file by massaging C source SYNOPSIS
mkstr [-] mesgfile prefix file ... DESCRIPTION
The mkstr utility creates a file containing error messages extracted from C source, and restructures the same C source, to utilize the cre- ated error message file. The intent of mkstr was to reduce the size of large programs and reduce swapping (see BUGS section below). The mkstr utility processes each of the specified files, placing a restructured version of the input in a file whose name consists of the specified prefix and the original name. A typical usage of mkstr is mkstr pistrings xx *.c This command causes all the error messages from the C source files in the current directory to be placed in the file pistrings and restruc- tured copies of the sources to be placed in files whose names are prefixed with ``xx''. Options: - Error messages are placed at the end of the specified message file for recompiling part of a large mkstred program. The mkstr utility finds error messages in the source by searching for the string 'error("' in the input stream. Each time it occurs, the C string starting at the '"' is stored in the message file followed by a null character and a new-line character; The new source is restruc- tured with lseek(2) pointers into the error message file for retrieval. char efilname = "/usr/lib/pi_strings"; int efil = -1; error(a1, a2, a3, a4) { char buf[256]; if (efil < 0) { efil = open(efilname, 0); if (efil < 0) err(1, "%s", efilname); } if (lseek(efil, (off_t)a1, SEEK_SET) < 0 || read(efil, buf, 256) <= 0) err(1, "%s", efilname); printf(buf, a2, a3, a4); } SEE ALSO
gencat(1), xstr(1), lseek(2) HISTORY
An mkstr utility appeared in 3.0BSD. BUGS
The mkstr utility was intended for the limited architecture of the PDP 11 family. Very few programs actually use it. The memory savings are negligible in modern computers. BSD
November 1, 2002 BSD

Check Out this Related Man Page

XSTR(1) 						    BSD General Commands Manual 						   XSTR(1)

NAME
xstr -- extract strings from C programs to implement shared strings SYNOPSIS
xstr [-cv] [-] [file ...] DESCRIPTION
The xstr utility 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 following options are available: - Read from the standard input. -c Extract the strings from the C source file or the standard 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 already. Repeated strings and strings which are suffixes of existing strings do not cause changes to the data base. -v Verbose mode. 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. The xstr utility 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 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 xstr after the C preprocessor is: cc -E name.c | xstr -c - cc -c x.c mv x.o name.o The xstr utility does not touch the file strings unless new items are added, thus 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'' does not touch strings SEE ALSO
mkstr(1) HISTORY
The xstr command appeared in 3.0BSD. 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. BSD
December 30, 1993 BSD

Featured Tech Videos