mkstr(1) [netbsd man page]

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

NAME

     mkstr -- create an error message file by massaging C source

SYNOPSIS

     mkstr [-] messagefile prefix file ...

DESCRIPTION

     mkstr creates files containing error messages extracted from C source, and restructures the same C source, to use the created error message
     file.  The intent of mkstr was to reduce the size of large programs and reduce swapping (see BUGS section below).

     mkstr 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 mkstr ed program.

     mkstr finds error messages in the source by searching for the string `error("' in the input stream.  Each time it occurs, the C string start-
     ing at the '"' is stored in the message file followed by a null character and a new-line character; The new source is restructured 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) {
	   oops:
				   perror(efilname);
				   exit 1 ;
			   }
		   }
		   if (lseek(efil, a1, 0) < 0 || read(efil, buf, 256) <= 0)
			   goto oops;
		   printf(buf, a2, a3, a4);
	   }

SEE ALSO

     xstr(1), lseek(2)

HISTORY

     mkstr appeared in 3.0BSD.

BUGS

     mkstr was intended for the limited architecture of the PDP-11 family.  Very few programs actually use it.	It is not an efficient method, the
     error messages should be stored in the program text.

BSD
								   June 6, 1993 							       BSD

xstr(1) 						      General Commands Manual							   xstr(1)

NAME

       xstr - Extracts strings from C programs to implement shared strings

SYNOPSIS

       xstr [-c] [file | -]

       The xstr command maintains a file called strings into which strings in component parts of a large program are hashed.

OPTIONS

       Extracts strings from the specified file.

DESCRIPTION

       The  strings extracted by xstr are replaced with references to this array. This serves to implement shared constant strings, most useful if
       they are also read-only.

       The following command extracts the strings from the C source in file, replacing string references by expressions of  the  form  (&xstr[num-
       ber]) for some number.  xstr -c file

       The  xstr  command  uses  file as input; the resulting C text is placed in the file x.c to then be compiled. The strings from this file are
       appended to the strings file if they are not there already. Repeated strings and strings that are suffixes of existing strings do not cause
       changes to the file.

       If  a  string  is a suffix of another string in the file, but the shorter string is seen first by xstr, both strings are placed in the file
       strings.

       After all components of a large program are compiled, a file xs.c declaring the common xstr space can be created by a command of  the  fol-
       lowing form: xstr

       Compile and load this xs.c file with the rest of the program.  Some C compilers may, by default, put strings in a read-only text section.

       The xstr command can also be used on a single file.  The following command creates files x.c and xs.c as before, without using or affecting
       a strings file in the same directory.  xstr file

       It may be useful to run xstr after the C preprocessor if any macro definitions yield strings or if there is conditional code that  contains
       strings that may not be needed.	The xstr command reads from its standard input when the argument - (dash) is given. An appropriate command
       sequence for running xstr after the C preprocessor is as follows: cc -E file.c | xstr -c - cc -c x.c mv x.o file.o

       The xstr command does not touch the file strings unless new items are added, thus make can avoid remaking xs.o unless truly necessary.

EXAMPLES

       To extract the strings from the C source in the file.c parameter, replacing string references by expressions of the  form  (&xstr[number]),
       enter: xstr -c file

	      An  appropriate declaration of the xstr array is prepended to file.  The resulting C text is placed in the file x.c, to then be com-
	      piled.  To declare the common xstr array space in the xs.c file, enter: xstr

FILES

       File that contains the extracted strings.  Modified C source.  C source for definition of array xstr.  Temporary file when the xstr command
       does not touch strings.

SEE ALSO

       Commands:  mkstr(1)

																	   xstr(1)