From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <20111115211034.GA6135@dinah> References: <20111115211034.GA6135@dinah> Date: Tue, 15 Nov 2011 13:49:39 -0800 Message-ID: From: David Leimbach To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=000e0cd4c5d0d8347504b1ccf63e Subject: Re: [9fans] all you yacc experts Topicbox-Message-UUID: 40ad5898-ead7-11e9-9d60-3106f5b1d025 --000e0cd4c5d0d8347504b1ccf63e Content-Type: text/plain; charset=ISO-8859-1 Pretty cool! On Tue, Nov 15, 2011 at 1:10 PM, Anthony Martin wrote: > Attached is a modified version of p9p yacc that > supports the Go grammar. I'll be sending a > version of Plan 9 yacc later today. > > The following is a description of the changes. > > 1. The %error-verbose directive is ignored. > > 2. A description of the final grammar is > printed before the state descriptions > in y.output. > > 3. The 'x' format for character literals is > now used instead of prefixing with a space. > > 4. The YYEMPTY define is now used to clear > the lookahead token (instead of an explicit > negative one). > > 5. Make yychar and yystate globals so they > can be inspected by external code. > > 5. Support C++ style // comments in actions. > > 6. Add a usage message. > > 7. Fix a few uses of sprint and strcpy. > > > I've also sent out a changeset to the Go > development list which adds support for > using Plan 9 yacc to generate the special > errors. > > One tiny nit is that Plan 9 uses the name > yytoknames for debugging where Bison uses > yytname. I've just used sed for this. > > Any questions? > Anthony > --000e0cd4c5d0d8347504b1ccf63e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Pretty cool!

On Tue, Nov 15, 2011 at 1:10= PM, Anthony Martin <ality@pbrane.org> wrote:
=A0Anthony

--000e0cd4c5d0d8347504b1ccf63e--