Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!caen!rphroy!hobbes.cs.gmr.com!tkacik
From: tkacik@hobbes.cs.gmr.com (Tom Tkacik CS/50)
Newsgroups: comp.sys.3b1
Subject: Re: more than 126 tokens in YACC ?
Message-ID: <55897@rphroy.UUCP>
Date: 13 Jun 91 12:39:28 GMT
References: <1214@wzlr.UUCP> <297@wmms.UUCP>
Sender: news@rphroy.UUCP
Reply-To: tkacik@hobbes.cs.gmr.com (Tom Tkacik CS/50)
Organization: G.M. Research Labs, Warren, MI
Lines: 26
Nntp-Posting-Host: hobbes.cs.gmr.com

In article <297@wmms.UUCP>, david@wmms.UUCP (David R. Mayne) writes:
|> In article <1214@wzlr.UUCP>, jms@wzlr.UUCP (Jack Stephens) writes:
|> >  fatal error: too many terminals, limit 127, line 125
|> > 
|> >  Will some kind soul tell me this is all a bad dream ?  Failing that,
|> >  how 'bout a work around?
|> 
|> The work around is to get byacc (Berkeley yacc).
|> Having the source code allows you to set the number of symbols
|> availible in the symbol table, and simply recompile, if
|> necessary.

There is no need to change the surce code to increase anything, as byacc
grows its tables dynamically.

|>             No changes are needed to compile this package on the 3b1.

Right.  I found byacc very easy to get working on my 3b1.  There isn't
even a file like /usr/lib/yaccpar to worry about, it's built
into the executable.

--
Tom Tkacik
GM Research Labs
tkacik@hobbes.cs.gmr.com
tkacik@kyzyl.mi.org