Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!samsung!rex!ukma!usenet.ins.cwru.edu!ncoast!allbery From: allbery@NCoast.ORG (Brandon S. Allbery KB8JRR) Newsgroups: comp.lang.perl Subject: Re: yacc stack overflow Message-ID: <1991Mar13.012932.1710@NCoast.ORG> Date: 13 Mar 91 01:29:32 GMT References: Reply-To: allbery@ncoast.ORG (Brandon S. Allbery KB8JRR) Followup-To: comp.lang.perl Organization: North Coast Public Access Un*x (ncoast) Lines: 29 As quoted from by emv@ox.com (Ed Vielmetti): +--------------- | smoke | yacc stack overflow in file /u1/emv/bin/smoke at line 238, next token "$verbose" | Execution of /u1/emv/bin/smoke aborted due to compilation errors. | | I get so tired of utilities with arbitrary, undocumented, | compiled-in limits. Don't you? | | it's a really weird one; i have a giant if {} elsif {} elsif {} thing | going, and adding one statement somewhere will cause the above error | to appear. +--------------- Yacc is one of those utilities with an arbitrary, compiled-in limit: the generated parser can handle only so much before it does this. I hit it with PL41 and terminfo.pl (yes, it will eventually be posted. If things will let up at the office for long enough, that is. grrr...). Question, which should be replied via MAIL: if this limit is in /usr/lib/yaccpar and I produce a modified version that dynamically allocates yacc stack space, can I post the diffs without getting AT&T on my case? ++Brandon -- Me: Brandon S. Allbery Ham: KB8JRR on 40m, 10m when time Internet: allbery@NCoast.ORG permits; also 2m, 220, 440, 1200 America OnLine: KB8JRR // Delphi: ALLBERY AMPR: kb8jrr.AmPR.ORG [44.70.4.88] uunet!usenet.ins.cwru.edu!ncoast!allbery KB8JRR @ WA8BXN.OH