1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
|
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html>
<head>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="Microsoft FrontPage 2.0">
<title>Geyacc: Command-line Options</title>
</head>
<body bgcolor="#FFFFFF">
<table border="0" width="100%">
<tr>
<td><font size="6"><strong>Command-line Options</strong></font></td>
<td align="right"><a href="parser.html"><img
src="../image/previous.gif" alt="Previous" border="0"
width="40" height="40"></a><a href="algorithm.html"><img
src="../image/next.gif" alt="Next" border="0" width="40"
height="40"></a></td>
</tr>
</table>
<hr size="1">
<p>The usual way to invoke <em>geyacc</em> is as follows:</p>
<blockquote>
<pre><font color="#800000">geyacc -o filename1 filename2</font></pre>
</blockquote>
<p>Here <font color="#800000"><tt>filename2</tt></font> is the
grammar file name, which usually ends with <font size="2">'</font><font
color="#800000"><tt>.y</tt></font><font size="2">'</font>, and
the Eiffel parser class is generated in <font color="#800000"><tt>filename1</tt></font>.
Thus, the <font color="#800000"><tt>geyacc -o foo.e foo.y </tt></font>yields
an Eiffel class in <font color="#800000"><tt>foo.e</tt></font>
describing a parser whose grammar is specified in <font
color="#800000"><tt>foo.y</tt></font>.</p>
<p><em>Geyacc</em> supports both traditional single-letter
options and mnemonic long option names. Long option names are
indicated with <font color="#800000"><tt>--</tt></font> instead
of <font color="#800000"><tt>-</tt></font>. When a long option
takes an argument, like <font color="#800000"><tt>--output-file</tt></font>,
connect the option name and the argument with <font
color="#800000"><tt>=</tt></font>. </p>
<p>Here is a list of options that can be used with <em>geyacc</em>,
alphabetized by short option:</p>
<dl>
<dt><a name="-t"><font color="#800000"><tt>-t</tt></font></a><font
color="#800000"><tt> classname<br>
--tokens=classname</tt></font></dt>
<dd>Write an extra class named <font color="#800000"><tt>classname</tt></font>
(in upper-case) containing integer constants for the
token type names defined in the grammar. This class is
saved in file <font color="#800000"><tt>classname.e</tt></font>
(in lower-case). This class is essential if you wish to
put the definition of routine <font color="#008080"><em><tt>read_token</tt></em></font>
in a separate class, because <font color="#008080"><em><tt>read_token</tt></em></font><font
color="#008080" size="2" face="Courier New"><em> </em></font>needs
to be able to refer to token type codes.<br>
<br>
[The options <font color="#800000"><tt>-d classname</tt></font>
and <font color="#800000"><tt>--defines=classname</tt></font>
are still available for compatibility with previous
version of <em>geyacc</em>. These options will be removed
in future releases.]</dd>
<dt><font color="#800000"><tt>-h<br>
-?<br>
--help</tt></font></dt>
<dd>Print a summary of the command-line options to <em>geyacc</em>
and exit.</dd>
<dt><font color="#800000"><tt>-o filename<br>
--output-file=filename</tt></font></dt>
<dd>Specify the name <font color="#800000"><tt>filename</tt></font>
for the parser file. If this option is not specified, the
parser is generated to the standard ouptut.</dd>
<dt><a name="-v"><font color="#800000"><tt>-v</tt></font></a><font
color="#800000"><tt> filename<br>
--verbose=filename</tt></font></dt>
<dd>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.</dd>
<dt><font color="#800000"><tt>-V<br>
--version</tt></font></dt>
<dd>Print the version number of <em>geyacc</em> and exit.</dd>
<dt><font color="#800000"><tt>-x</tt></font></dt>
<dd>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.</dd>
</dl>
<hr size="1">
<table border="0" width="100%">
<tr>
<td><address>
<font size="2"><b>Copyright 1999</b></font><font
size="1"><b>, </b></font><font size="2"><strong>Eric
Bezault</strong></font><strong> </strong><font
size="2"><br>
<strong>mailto:</strong></font><a
href="mailto:ericb@gobosoft.com"><font size="2">ericb@gobosoft.com</font></a><font
size="2"><br>
<strong>http:</strong></font><a
href="http://www.gobosoft.com"><font size="2">//www.gobosoft.com</font></a><font
size="2"><br>
<strong>Last Updated:</strong> 17 February 1999</font><br>
<!--webbot bot="PurpleText"
preview="
$Date: 1999/06/12 18:56:47 $
$Revision: 1.9 $"
-->
</address>
</td>
<td align="right" valign="top"><a
href="http://www.gobosoft.com"><img
src="../image/home.gif" alt="Home" border="0" width="40"
height="40"></a><a href="index.html"><img
src="../image/toc.gif" alt="Toc" border="0" width="40"
height="40"></a><a href="parser.html"><img
src="../image/previous.gif" alt="Previous" border="0"
width="40" height="40"></a><a href="algorithm.html"><img
src="../image/next.gif" alt="Next" border="0" width="40"
height="40"></a></td>
</tr>
</table>
</body>
</html>
|
