GAWK: Effective AWK Programming

More documents

Recommendations

Info

142 GAWK: Effective AWK Programmingexisting practice. The proposed rules have special cases that make it possible to produce a‘\’ preceding the matched text. This is shown in Table 8.3.You type sub sees sub generates\\\\\\& \\\& a literal ‘\&’\\\\& \\& a literal ‘\’, followed by the matched text\\& \& a literal ‘&’\\q \q a literal ‘\q’\\\\ \\ \\Table 8.3: Proposed rules for sub and backslashIn a nutshell, at the runtime level, there are now three special sequences of characters(‘\\\&’, ‘\\&’ and ‘\&’) whereas historically there was only one. However, as in the historicalcase, any ‘\’ that is not part of one of these three sequences is not special and appears inthe output literally.gawk 3.0 and 3.1 follow these proposed POSIX rules for sub and gsub. The POSIXstandard took much longer to be revised than was expected in 1996. The 2001 standarddoes not follow the above rules. Instead, the rules there are somewhat simpler. The resultsare similar except for one case.The 2001 POSIX rules state that ‘\&’ in the replacement string produces a literal ‘&’,‘\\’ produces a literal ‘\’, and ‘\’ followed by anything else is not special; the ‘\’ is placedstraight into the output. These rules are presented in Table 8.4.You type sub sees sub generates\\\\\\& \\\& a literal ‘\&’\\\\& \\& a literal ‘\’, followed by the matched text\\& \& a literal ‘&’\\q \q a literal ‘\q’\\\\ \\ \Table 8.4: POSIX 2001 rules for subThe only case where the difference is noticeable is the last one: ‘\\\\’ is seen as ‘\\’ andproduces ‘\’ instead of ‘\\’.Starting with version 3.1.4, gawk follows the POSIX rules when ‘--posix’ is specified(see Section 11.2 [Command-Line Options], page 177). Otherwise, it continues to followthe 1996 proposed rules, since, as of this writing, that has been its behavior for over sevenyears.NOTE: At the next major release, gawk will switch to using the POSIX 2001rules by default.The rules for gensub are considerably simpler. At the runtime level, whenever gawk seesa ‘\’, if the following character is a digit, then the text that matched the corresponding
Chapter 8: Functions 143parenthesized subexpression is placed in the generated output. Otherwise, no matter whatcharacter follows the ‘\’, it appears in the generated text and the ‘\’ does not, as shown inTable 8.5.You type gensub sees gensub generates& & the matched text\\& \& a literal ‘&’\\\\ \\ a literal ‘\’\\\\& \\& a literal ‘\’, then the matched text\\\\\\& \\\& a literal ‘\&’\\q \q a literal ‘q’Table 8.5: Escape Sequence Processing for gensubBecause of the complexity of the lexical and runtime level processing and the specialcases for sub and gsub, we recommend the use of gawk and gensub when you have to dosubstitutions.Advanced Notes: Matching the Null StringIn awk, the ‘*’ operator can match the null string. This is particularly important for thesub, gsub, and gensub functions. For example:$ echo abc | awk ’{ gsub(/m*/, "X"); print }’⊣ XaXbXcXAlthough this makes a certain amount of sense, it can be surprising.8.1.4 Input/Output FunctionsThe following functions relate to input/output (I/O). Optional parameters are enclosed insquare brackets ([ ]):close(filename [, how])Close the file filename for input or output. Alternatively, the argument may bea shell command that was used for creating a coprocess, or for redirecting toor from a pipe; then the coprocess or pipe is closed. See Section 4.8 [ClosingInput and Output Redirections], page 71, for more information.When closing a coprocess, it is occasionally useful to first close one end of thetwo-way pipe and then to close the other. This is done by providing a secondargument to close. This second argument should be one of the two stringvalues "to" or "from", indicating which end of the pipe to close. Case inthe string does not matter. See Section 10.2 [Two-Way Communications withAnother Process], page 170, which discusses this feature in more detail andgives an example.fflush([filename])Flush any buffered output associated with filename, which is either a file openedfor writing or a shell command for redirecting output to a pipe or coprocess.
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: 96 GAWK: Effective AWK Programming6
Page 110 and 111: 98 GAWK: Effective AWK Programmingt
Page 112 and 113: 100 GAWK: Effective AWK Programming
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:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 304 and 305:
Page 306 and 307:
Page 308 and 309:
Page 310 and 311:
Page 312 and 313:
Page 314 and 315:
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?