Intel XENIX 286 Programmers Guide (86) - Tenox.tc
Intel XENIX 286 Programmers Guide (86) - Tenox.tc Intel XENIX 286 Programmers Guide (86) - Tenox.tc
XENIX Programming Programming Commands xstr - Syntax Extracts strings from C programs. xstr [-c] [-] [ file 1 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 and is most useful if they are also read-only strings. The command xstr -c name will extract 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 that 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 xs.c declaring the common xstr space can be created by a command of the form xstr -c name 1 name2 name3 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 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 containing strings that may not, in fact, be needed. xstr reads from its standard input when the argu ment - is given. An appropriate command sequence for running xstr after the C preprocessor is cc -E name.c I xstr -c cc -c x.c mv x .o name.o B-121
Programming Commands XENIX Programming xstr (continued) xstr does not touch the file strings unless new items are added. Thus, make 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* Temp file when xstr nam e doesn't touch strings See Also mkstr Credit This utility was developed at the University of California at Berkeley and is used with permission. Notes 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 even when placing just the longer one there will do. 8-122
- Page 336 and 337: XENIX Programming Programming Comma
- Page 338 and 339: XENIX Programming Programming Comma
- Page 340 and 341: XENIX Programming Programming Comma
- Page 342 and 343: XENIX Programming Programming Comma
- Page 344 and 345: XENIX Programming lex (continued) E
- Page 346 and 347: XENIX Programming Programming Comma
- Page 348 and 349: XENIX Programming Programming Comma
- Page 350 and 351: XENIX Programming Programming Comma
- Page 352 and 353: XENIX Programming Programming Comma
- Page 354 and 355: XENIX Programming Programming Comma
- Page 356 and 357: XENIX Programming Programming Comma
- Page 358 and 359: XENIX Programming Programming Comma
- Page 360 and 361: XENIX Programm ing Programming Comm
- Page 362 and 363: XENIX Programming Programming Comma
- Page 364 and 365: XENIX Programming prs (continued) :
- Page 366 and 367: XENIX Programming Programming Comma
- Page 368 and 369: XENIX Programming Programm ing Comm
- Page 370 and 371: XENIX Programming Programming Comma
- Page 372 and 373: XENIX Programming Programm ing Comm
- Page 374 and 375: XENIX Programming Programming Comma
- Page 376 and 377: XENIX Programming Programming Comma
- Page 378 and 379: XENIX Programming Programming Comma
- Page 380 and 381: XENIX Programming Programming Comma
- Page 382 and 383: XENIX Programming Programming Comma
- Page 384 and 385: XENIX Programming Programming Comma
- Page 388 and 389: XENIX Programming Programming Comma
- Page 390 and 391: Intel Publications Copies of the fo
- Page 392 and 393: INDEX Note: For a master index to t
- Page 394 and 395: XENIX Programming lint, B-80 thru B
- Page 396 and 397: XENIX Programming fscanf, A-12 get,
- Page 398 and 399: XENIX Programming maketemp, 11-8, B
- Page 400 and 401: XENIX Programming Segments, 2-19, 2
- Page 402 and 403: XENIX Programming yacc.acts, B-123
- Page 404 and 405: REQUE.ST FOR READER'S COMMENTS XENI
- Page 406: I I
Programming Commands <strong>XENIX</strong> Programming<br />
xstr (continued)<br />
xstr does not touch the file strings unless new items are added. Thus, make can avoid<br />
remaking xs.o unless truly necessary.<br />
Files<br />
strings Data base of strings<br />
x.c Massaged C source<br />
xs.c C source for definition of array xstr<br />
/tmp/xs* Temp file when xstr nam e doesn't touch strings<br />
See Also<br />
mkstr<br />
Credit<br />
This utility was developed at the University of California at Berkeley and is used with<br />
permission.<br />
Notes<br />
If a string is a suffix of another string in the data base, but the shorter string is seen<br />
first by xstr, both strings will be placed in the data base even when placing just the<br />
longer one there will do.<br />
8-122