Contents of the gawk Distribution

The gawk distribution has a number of C source files, documentation files, subdirectories and files related to the configuration process (see section Compiling and Installing gawk on Unix), and several subdirectories related to different, non-Unix, operating systems.

various `.c', `.y', and `.h' files

These files are the actual gawk source code.

`README'

`README_d/README.*'

Descriptive files: `README' for gawk under Unix, and the rest for the various hardware and software combinations.

`INSTALL'

A file providing an overview of the configuration and installation process.

`PORTS'

A list of systems to which gawk has been ported, and which have successfully run the test suite.

`ACKNOWLEDGMENT'

A list of the people who contributed major parts of the code or documentation.

`ChangeLog'

A detailed list of source code changes as bugs are fixed or improvements made.

`NEWS'

A list of changes to gawk since the last release or patch.

`COPYING'

The GNU General Public License.

`FUTURES'

A brief list of features and/or changes being contemplated for future releases, with some indication of the time frame for the feature, based on its difficulty.

`LIMITATIONS'

A list of those factors that limit gawk's performance. Most of these depend on the hardware or operating system software, and are not limits in gawk itself.

`POSIX.STD'

A description of one area where the POSIX standard for awk is incorrect, and how gawk handles the problem.

`PROBLEMS'

A file describing known problems with the current release.

`doc/awkforai.txt'

A short article describing why gawk is a good language for AI (Artificial Intelligence) programming.

`doc/README.card'

`doc/ad.block'

`doc/awkcard.in'

`doc/cardfonts'

`doc/colors'

`doc/macros'

`doc/no.colors'

`doc/setter.outline'

The troff source for a five-color awk reference card. A modern version of troff, such as GNU Troff (groff) is needed to produce the color version. See the file `README.card' for instructions if you have an older troff.

`doc/gawk.1'

The troff source for a manual page describing gawk. This is distributed for the convenience of Unix users.

`doc/gawk.texi'

The Texinfo source file for this book. It should be processed with TeX to produce a printed document, and with makeinfo to produce an Info file.

`doc/gawk.info'

The generated Info file for this book.

`doc/igawk.1'

The troff source for a manual page describing the igawk program presented in section An Easy Way to Use Library Functions.

`doc/Makefile.in'

The input file used during the configuration process to generate the actual `Makefile' for creating the documentation.

`Makefile.in'

`acconfig.h'

`aclocal.m4'

`configh.in'

`configure.in'

`configure'

`custom.h'

`missing/*'

These files and subdirectory are used when configuring gawk for various Unix systems. They are explained in detail in section Compiling and Installing gawk on Unix.

`awklib/extract.awk'

`awklib/Makefile.in'

The `awklib' directory contains a copy of `extract.awk' (see section Extracting Programs from Texinfo Source Files), which can be used to extract the sample programs from the Texinfo source file for this book, and a `Makefile.in' file, which configure uses to generate a `Makefile'. As part of the process of building gawk, the library functions from section A Library of awk Functions, and the igawk program from section An Easy Way to Use Library Functions, are extracted into ready to use files. They are installed as part of the installation process.

`atari/*'

Files needed for building gawk on an Atari ST. See section Installing gawk on the Atari ST, for details.

`pc/*'

Files needed for building gawk under MS-DOS and OS/2. See section MS-DOS and OS/2 Installation and Compilation, for details.

`vms/*'

Files needed for building gawk under VMS. See section How to Compile and Install gawk on VMS, for details.

`test/*'

A test suite for gawk. You can use `make check' from the top level gawk directory to run your version of gawk against the test suite. If gawk successfully passes `make check' then you can be confident of a successful port.

Go to the first, previous, next, last section, table of contents.