[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 00/17] RFC: multiple start symbols

From: Paul Eggert
Subject: Re: [PATCH 00/17] RFC: multiple start symbols
Date: Sun, 20 Sep 2020 19:55:36 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0

My quick reaction is that this looks like a good thing to have, but the most important part is missing: the documentation patches. These should cover:

* Why have multiple start symbols? (See, for example, the motivating discussion for this feature on page 6 of the RACK manual <>.)

* Suppose Bison didn't have multiple start symbols; how could you achieve their effect? (This is already in the Bison manual, I think.)

* What is the advantage of multiple start symbols over that simulation?

* Maybe contrast to how other Yacc-like parser generators do it? (Or at least, steal good ideas from them. :-) These come to mind:

** RACK (see page 27 of its manual)
** Zyacc <>

Disclaimer - I'm biased re RACK as it was written by a friend-of-a-friend.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]