21.07.2015 Views

GAWK: Effective AWK Programming

GAWK: Effective AWK Programming

GAWK: Effective AWK Programming

SHOW MORE
SHOW LESS

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

280 <strong>G<strong>AWK</strong></strong>: <strong>Effective</strong> <strong>AWK</strong> <strong>Programming</strong>page 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 ‘<strong>AWK</strong>H’. 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

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!