Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!bionet!agate!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.234823.12036@NCoast.ORG> Date: 13 Mar 91 23:48:23 GMT References: <1991Mar13.012932.1710@NCoast.ORG> Reply-To: allbery@ncoast.ORG (Brandon S. Allbery KB8JRR) Followup-To: comp.lang.perl Organization: North Coast Public Access Un*x (ncoast) Lines: 24 As quoted from <1991Mar13.012932.1710@NCoast.ORG> by allbery@NCoast.ORG (Brandon S. Allbery KB8JRR): +--------------- | /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? +--------------- Actually, the answer *may* be "yes" --- AT&T has already permitted generated y.tab.c's to be distributed. In any case, I got two main suggestions: byacc (which is freely hackable) and bison (which automatically grows the stack). In my case, bison is out: I had the same problem with some home-grown parsers... which must be linked with proprietary libraries. And I've explained to a brick wall (read: rms) why that can't change. I *have* byacc, so that's an idea. But many people don't have it, and do have Perl, and therefore have a problem. Suggestions? ++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