geyacc(1)

geyacc1

Parser generator for eiffel

Usage

geyacc [options] file

Overview

This manual page documents briefly the geyacc, command. This manual page was written for the Debian GNU/Linux distribution because the original program does not have a manual page. Instead, it has documentation in HTML format; see below.

geyacc is a program that reads an input file containing the description of a parser and generates an Eiffel class file to implement it.

Options

The programs follow the usual GNU command line syntax, with long options starting with two dashes (`-').

-t classname
--tokens=classname

Write an extra class named classname (in upper-case) containing integer constants for the token type names defined in the grammar. This class is saved in file classname.e (in lower-case). This class is essential if you wish to put the definition of routine read_token in a separate class, because read_token needs to be able to refer to token type codes. This class also contains the routine token_name which is particularly useful to make debugging messages more human-readable.

-kfilename
--tokens-file=filename

Name of the file where the extra class containing integer constants for the token type names will be written. If the -t or --tokens option has not been specified, then nothing will be written to that file.

-h
-?
--help

Print a summary of the command-line options to geyacc and exit.

-o filename
--output-file=filename

Specify the name filename for the parser file. If this option is not specified, the parser is generated to the standard ouptut.

-v filename
--verbose=filename

Write an extra output file containing verbose descriptions of the parser states and what is done for each type of look-ahead token in that state. This file also describes all the conflicts, both those resolved by operator precedence and the unresolved ones.

-V
--version

Print the version number of geyacc and exit.

-x

Write each semantic action into a separate routine. The default is to write all semantic actions into the same routine, which can become too large for C back-end compilers to handle.

Releases

4 releases since Debian 2.2 (Potato); the text changed 2 times.

  1. 2.2–3.0
  2. 3.1
  3. 4.0

--tokens-file since Debian 3.1 (Sarge); -k since Debian 3.1 (Sarge).

Author

This manual page was written by Oliver Elphick <[email protected]> and updated by Julien Lemoine <[email protected]> for the Debian GNU/Linux system (but may be used by others).

From gobo 3.3-6 in Debian 4.0 (Etch). Parsed by carta from the page's man source.