rfg@MCC.COM (Ron Guilmette) (06/06/89)
I believe that bison (1.01) fails to actually do an "unlink" on its output file if that file exists already. Unfortunately, if the output file *does* already exist, and if there are one or more hard links to it (other than the output file itself) then Bison's unwillingness to actually unlink before writting to the output file can causes undesriable (and perhaps even disasterous) consequences. // rfg
montnaro@sprite.crd.ge.com (Skip Montanaro) (10/19/89)
In the Bison (version 1.01) manual section describing the RPN calculator,
the node definition for the "Rpcalc Decls" node is
@node Rpcalc Decls, Rpcalc Lexer, RPN calc, RPN calc
The menu definition is
@menu
* Decls: Rpcalc Decls. Bison and C declarations for rpcalc.
* Rules: Rpcalc Rules. Grammar Rules for rpcalc, with explanation.
* Input: Rpcalc Input. Explaining the rules for @code{input}.
* Line: Rpcalc Line. Explaining the rules for @code{line}.
* Expr: Rpcalc Expr. Explaining the rules for @code{expr}.
* Lexer: Rpcalc Lexer. The lexical analyzer.
* Main: Rpcalc Main. The controlling function.
* Error: Rpcalc Error. The error reporting function.
* Gen: Rpcalc Gen. Running Bison on the grammar file.
* Comp: Rpcalc Compile. Run the C compiler on the output code.
@end menu
Using 'n' in info the walk through the example causes the 2nd, 3rd, and 4th
menu items to be missed. For consistency's sake, the next field of the
"Rpcalc Decls" node should be "Rpcalc Rules", not "Rpcalc Lexer".
--
Skip Montanaro (montanaro@crdgw1.ge.com)