GAWK: Effective AWK Programming

More documents

Recommendations

Info

280 GAWK: Effective AWK Programmingpage 56, and Section 4.6 [Redirecting Output of print and printf], page 66), which is justtoo foreign a concept for Tandem.To build a Tandem executable from source, download all of the files so that the file nameson the Tandem box conform to the restrictions of D20. For example, ‘array.c’ becomes‘ARRAYC’, and ‘awk.h’ becomes ‘AWKH’. The totally Tandem-specific files are in the ‘tandem’“subvolume” (‘unsupported/tandem’ in the gawk distribution) and should be copied to themain source directory before building gawk.The file ‘compit’ can then be used to compile and bind an executable. Alas, there is noconfigure or make.Usage is the same as for Unix, except that D20 requires all ‘{’ and ‘}’ characters to beescaped with ‘~’ on the command line (but not in script files). Also, the standard Tandemsyntax for ‘/in filename,out filename/’ must be used instead of the usual Unix ‘’ for file redirection. (Redirection options on getline, print etc., are supported.)The ‘-mr val’ option (see Section 11.2 [Command-Line Options], page 177) has been“stolen” to enable Tandem users to process fixed-length records with no “end-of-line” character.That is, ‘-mr 74’ tells gawk to read the input file as fixed 74-byte records.B.5 Reporting Problems and BugsThere is nothing more dangerous than a bored archeologist.The Hitchhiker’s Guide to the GalaxyIf you have problems with gawk or think that you have found a bug, please report it tothe developers; we cannot promise to do anything but we might well want to fix it.Before reporting a bug, make sure you have actually found a real bug. Carefully rereadthe documentation and see if it really says you can do what you’re trying to do. If it’s notclear whether you should be able to do something or not, report that too; it’s a bug in thedocumentation!Before reporting a bug or trying to fix it yourself, try to isolate it to the smallest possibleawk program and input data file that reproduces the problem. Then send us the programand data file, some idea of what kind of Unix system you’re using, the compiler you used tocompile gawk, and the exact results gawk gave you. Also say what you expected to occur;this helps us decide whether the problem is really in the documentation.Once you have a precise problem, send email to bug-gawk@gnu.org.Please include the version number of gawk you are using. You can get this informationwith the command ‘gawk --version’. Using this address automatically sends a carbon copyof your mail to me. If necessary, I can be reached directly at arnold@skeeve.com. Thebug reporting address is preferred since the email list is archived at the GNU Project. Allemail should be in English, since that is my native language.Caution: Do not try to report bugs in gawk by posting to the Usenet/Internet newsgroupcomp.lang.awk. While the gawk developers do occasionally read this newsgroup, there isno guarantee that we will see your posting. The steps described above are the officialrecognized ways for reporting bugs.NOTE: Many distributions of GNU/Linux and the various BSD-based operatingsystems have their own bug reporting systems. If you report a bug
Appendix B: Installing gawk 281using your distribution’s bug reporting system, please also send a copy tobug-gawk@gnu.org.This is for two reasons. First, while some distributions forward bug reports“upstream” to the GNU mailing list, many don’t, so there is a good chancethat the gawk maintainer won’t even see the bug report! Second, mail to theGNU list is archived, and having everything at the GNU project keeps thingsself-contained and not dependant on other web sites.Non-bug suggestions are always welcome as well. If you have questions about thingsthat are unclear in the documentation or are just obscure features, ask me; I will try to helpyou out, although I may not have the time to fix the problem. You can send me electronicmail at the Internet address noted previously.If you find bugs in one of the non-Unix ports of gawk, please send an electronic mailmessage to the person who maintains that port. They are named in the following list, aswell as in the ‘README’ file in the gawk distribution. Information in the ‘README’ file shouldbe considered authoritative if it conflicts with this book.The people maintaining the non-Unix ports of gawk are as follows:MS-DOSMS-Windows using MINGWTandemTandem (POSIX-compliant)VMSScott Deifik, scottd.mail@sbcglobal.net.Eli Zaretskii, eliz@gnu.org.Stephen Davies, scldad@sdc.com.au.Ralf Wildenhues Ralf.Wildenhues@gmx.dePat Rankin, rankin@pactechdata.com.z/OS (OS/390)Dave Pitts, pitts@cozx.com.If your bug is also reproducible under Unix, please send a copy of your report to thebug-gawk@gnu.org email list as well.B.6 Other Freely Available awk ImplementationsIt’s kind of fun to put comments like this in your awk code.// Do C++ comments work? answer: yes! of courseMichael BrennanThere are a number of other freely available awk implementations. This section brieflydescribes where to get them:Unix awk Brian Kernighan has made his implementation of awk freely available. Youcan retrieve this version via the World Wide Web from his home page. It isavailable in several archive formats:Shell archivehttp://www.cs.princeton.edu/~bwk/btl.mirror/awk.shar
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:
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: 230 GAWK: Effective AWK Programming
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?