GAWK: Effective AWK Programming

More documents

Recommendations

Info

190 GAWK: Effective AWK Programmingif ((k = index("0123456789", c)) > 0)k-- # adjust for 1-basing in awkelse if ((k = index("abcdef", c)) > 0)k += 9ret = ret * 16 + k}} else if (str ~ /^[-+]?([0-9]+([.][0-9]*([Ee][0-9]+)?)?|([.][0-9]+([Ee][-+]?[0-9]+# decimal number, possibly floating pointret = str + 0} elseret = "NOT-A-NUMBER"}return ret# BEGIN { # gawk test harness# a[1] = "25"# a[2] = ".31"# a[3] = "0123"# a[4] = "0xdeadBEEF"# a[5] = "123.45"# a[6] = "1.e3"# a[7] = "1.32"# a[7] = "1.32E2"## for (i = 1; i in a; i++)# print a[i], strtonum(a[i]), mystrtonum(a[i])# }The function first looks for C-style octal numbers (base 8). If the input string matches aregular expression describing octal numbers, then mystrtonum loops through each characterin the string. It sets k to the index in "01234567" of the current octal digit. Since thereturn value is one-based, the ‘k--’ adjusts k so it can be used in computing the returnvalue.Similar logic applies to the code that checks for and converts a hexadecimal value, whichstarts with ‘0x’ or ‘0X’. The use of tolower simplifies the computation for finding thecorrect numeric value for each hexadecimal digit.Finally, if the string matches the (rather complicated) regex for a regular decimal integeror floating-point number, the computation ‘ret = str + 0’ lets awk convert the value to anumber.A commented-out test program is included, so that the function can be tested with gawkand the results compared to the built-in strtonum function.12.2.3 AssertionsWhen writing large programs, it is often useful to know that a condition or set of conditionsis true. Before proceeding with a particular computation, you make a statement about what
Chapter 12: A Library of awk Functions 191you believe to be the case. Such a statement is known as an assertion. The C languageprovides an header file and corresponding assert macro that the programmercan use to make assertions. If an assertion fails, the assert macro arranges to print adiagnostic message describing the condition that should have been true but was not, andthen it kills the program. In C, using assert looks this:#include int myfunc(int a, double b){assert(a = 17.1);...}If the assertion fails, the program prints a message similar to this:prog.c:5: assertion failed: a = 17.1The C language makes it possible to turn the condition into a string for use in printingthe diagnostic message. This is not possible in awk, so this assert function also requires astring version of the condition that is being tested. Following is the function:# assert --- assert that a condition is true. Otherwise exit.function assert(condition, string){if (! condition) {printf("%s:%d: assertion failed: %s\n",FILENAME, FNR, string) > "/dev/stderr"_assert_exit = 1exit 1}}END {if (_assert_exit)exit 1}The assert function tests the condition parameter. If it is false, it prints a messageto standard error, using the string parameter to describe the failed condition. It then setsthe variable _assert_exit to one and executes the exit statement. The exit statementjumps to the END rule. If the END rules finds _assert_exit to be true, it exits immediately.The purpose of the test in the END rule is to keep any other END rules from running.When an assertion fails, the program should exit immediately. If no assertions fail, then_assert_exit is still false when the END rule is run normally, and the rest of the program’sEND rules execute. For all of this to work correctly, ‘assert.awk’ must be the first sourcefile read by awk. The function can be used in a program in the following way:function myfunc(a, b){assert(a = 17.1, "a = 17.1")...
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: 140 GAWK: Effective AWK Programming
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

Create successful ePaper yourself

Delete template?

Save as template?