Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news.iecc.com!.POSTED!nerds-end From: glen herrmannsfeldt Newsgroups: comp.compilers Subject: Re: Formatting of Language LRMs Date: Sun, 3 Aug 2014 04:37:37 +0000 (UTC) Organization: Aioe.org NNTP Server Lines: 20 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <14-08-003@comp.compilers> References: <14-06-010@comp.compilers> <14-06-013@comp.compilers> NNTP-Posting-Host: news.iecc.com X-Trace: miucha.iecc.com 1407088918 75567 2001:470:1f07:1126:0:676f:7373:6970 (3 Aug 2014 18:01:58 GMT) X-Complaints-To: abuse@iecc.com NNTP-Posting-Date: Sun, 3 Aug 2014 18:01:58 +0000 (UTC) Keywords: parse, tools Posted-Date: 03 Aug 2014 14:01:58 EDT X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: csiph.com comp.compilers:1359 lpsantil@gmail.com wrote: > Personally, I enjoy Wirth Syntax Notation (WSN)[1] more than BNF/EBNF. > There are wikipedia entries, I believe, also incorrectly identifies > the PL/0 language grammar (also Wirth's work)[2][3] as EBNF when it is > WSN. After a previous post, it occurred to me that a tool that would convert yacc input into printable BNF might be useful. That way, the printed version would agree with the compiled version. > [1] http://en.wikipedia.org/wiki/Wirth_syntax_notation > [2] http://en.wikipedia.org/wiki/Recursive_descent_parser > [3] http://en.wikipedia.org/wiki/PL/0 -- glen [I'm not sure how useful it would be, since most practical yacc grammars use precedence and other hacks to accept a language that's not the same as the mechanically generated BNF would. -John]