GAWK: Effective AWK Programming

More documents

Recommendations

Info

254 GAWK: Effective AWK ProgrammingThe stack is initialized with ARGV[1], which will be ‘/dev/stdin’. The main loop comesnext. Input lines are read in succession. Lines that do not start with ‘@include’ are printedverbatim. If the line does start with ‘@include’, the file name is in $2. pathto is called togenerate the full path. If it cannot, then we print an error message and continue.The next thing to check is if the file is included already. The processed array is indexedby the full file name of each included file and it tracks this information for us. If the file isseen again, a warning message is printed. Otherwise, the new file name is pushed onto thestack and processing continues.Finally, when getline encounters the end of the input file, the file is closed and thestack is popped. When stackptr is less than zero, the program is done:stackptr = 0input[stackptr] = ARGV[1] # ARGV[1] is first filefor (; stackptr >= 0; stackptr--) {while ((getline < input[stackptr]) > 0) {if (tolower($1) != "@include") {printcontinue}fpath = pathto($2)if (fpath == "") {printf("igawk:%s:%d: cannot find %s\n",input[stackptr], FNR, $2) > "/dev/stderr"continue}if (! (fpath in processed)) {processed[fpath] = input[stackptr]input[++stackptr] = fpath # push onto stack} elseprint $2, "included in", input[stackptr],"already included in",processed[fpath] > "/dev/stderr"}close(input[stackptr])}}’ # close quote ends ‘expand_prog’ variableprocessed_program=‘gawk -- "$expand_prog" /dev/stdin
Chapter 13: Practical awk Programs 255The shell construct ‘‘...‘’ is called command substitution. The output of the commandbetween the two backquotes (grave accents) is substituted into the command line. It is savedas a single string, even if the results contain whitespace.The expanded program is saved in the variable processed_program. It’s done in thesesteps:1. Run gawk with the ‘@include’-processing program (the value of the expand_prog shellvariable) on standard input.2. Standard input is the contents of the user’s program, from the shell variable program.Its contents are fed to gawk via a here document.3. The results of this processing are saved in the shell variable processed_program byusing command substitution.The last step is to call gawk with the expanded program, along with the original optionsand command-line arguments that the user supplied.eval gawk $opts -- ’"$processed_program"’ ’"$@"’The eval command is a shell construct that reruns the shell’s parsing process. Thiskeeps things properly quoted.This version of igawk represents my fourth attempt at this program. There are four keysimplifications that make the program work better:• Using ‘@include’ even for the files named with ‘-f’ makes building the initial collectedawk program much simpler; all the ‘@include’ processing can be done once.• Not trying to save the line read with getline in the pathto function when testing forthe file’s accessibility for use with the main program simplifies things considerably.• Using a getline loop in the BEGIN rule does it all in one place. It is not necessary tocall out to a separate loop for processing nested ‘@include’ statements.• Instead of saving the expanded program in a temporary file, putting it in a shell variableavoids some potential security problems. This has the disadvantage that the script reliesupon more features of the sh language, making it harder to follow for those who aren’tfamiliar with sh.Also, this program illustrates that it is often worthwhile to combine sh and awk programmingtogether. You can usually accomplish quite a lot, without having to resort tolow-level programming in C or C++, and it is frequently easier to do certain kinds of stringand argument manipulation using the shell than it is in awk.Finally, igawk shows that it is not always necessary to add new features to a program;they can often be layered on top. With igawk, there is no real reason to build ‘@include’processing into gawk itself.As an additional example of this, consider the idea of having two files in a directory inthe search path:‘default.awk’This file contains a set of default library functions, such as getopt and assert.‘site.awk’This file contains library functions that are specific to a site or installation;i.e., locally developed functions. Having a separate file allows ‘default.awk’ to
Page 1 and 2:
GAWK: Effective AWK ProgrammingA Us
Page 3:
To Miriam, for making me complete.T
Page 6 and 7:
iiGAWK: Effective AWK ProgrammingTa
Page 8 and 9:
ivGAWK: Effective AWK Programming5
Page 10 and 11:
viGAWK: Effective AWK Programming10
Page 12 and 13:
viiiGAWK: Effective AWK Programming
Page 14 and 15:
2 GAWK: Effective AWK Programmingea
Page 16 and 17:
4 GAWK: Effective AWK ProgrammingAf
Page 18 and 19:
6 GAWK: Effective AWK ProgrammingCh
Page 20 and 21:
8 GAWK: Effective AWK ProgrammingGN
Page 22 and 23:
10 GAWK: Effective AWK Programmingt
Page 24 and 25:
12 GAWK: Effective AWK ProgrammingT
Page 26 and 27:
14 GAWK: Effective AWK Programmingp
Page 28 and 29:
16 GAWK: Effective AWK Programming$
Page 30 and 31:
Page 32 and 33:
20 GAWK: Effective AWK Programming
Page 34 and 35:
22 GAWK: Effective AWK ProgrammingH
Page 36 and 37:
24 GAWK: Effective AWK Programming2
Page 38 and 39:
26 GAWK: Effective AWK Programming\
Page 40 and 41:
28 GAWK: Effective AWK Programming[
Page 42 and 43:
30 GAWK: Effective AWK Programmings
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
40 GAWK: Effective AWK Programming$
Page 54 and 55:
42 GAWK: Effective AWK Programmingh
Page 56 and 57:
Page 58 and 59:
46 GAWK: Effective AWK ProgrammingB
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
54 GAWK: Effective AWK Programming{
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
62 GAWK: Effective AWK Programming%
Page 76 and 77:
Page 78 and 79:
66 GAWK: Effective AWK ProgrammingI
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
72 GAWK: Effective AWK ProgrammingS
Page 86 and 87:
74 GAWK: Effective AWK Programmingo
Page 88 and 89:
Page 90 and 91:
78 GAWK: Effective AWK Programmingh
Page 92 and 93:
80 GAWK: Effective AWK Programmingf
Page 94 and 95:
82 GAWK: Effective AWK Programmingx
Page 96 and 97:
Page 98 and 99:
86 GAWK: Effective AWK ProgrammingA
Page 100 and 101:
88 GAWK: Effective AWK ProgrammingU
Page 102 and 103:
90 GAWK: Effective AWK ProgrammingI
Page 104 and 105:
92 GAWK: Effective AWK ProgrammingS
Page 106 and 107:
94 GAWK: Effective AWK ProgrammingA
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217: 204 GAWK: Effective AWK Programming
Page 316 and 317:
Page 318 and 319:
Page 320 and 321:
Page 322 and 323:
Page 324 and 325:
Page 326 and 327:
Page 328 and 329:
Page 330 and 331:
Page 332 and 333:
Page 334 and 335:
Page 336 and 337:
Page 338 and 339:
Page 340 and 341:
Page 342 and 343:
Page 344 and 345:
Page 346 and 347:
Page 348 and 349:
Page 350 and 351:
Page 352 and 353:
Page 354 and 355:
Page 356 and 357:
Page 358 and 359:
Page 360 and 361:
Page 362 and 363:
Page 364:
show all

GAWK: Effective AWK Programming

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?