Re: Formatting of Language LRMs

glen herrmannsfeldt <gah@ugcs.caltech.edu>
Sun, 3 Aug 2014 04:37:37 +0000 (UTC)

          From comp.compilers
Related articles
[4 earlier articles]
Re: Formatting of Language LRMs kaz@kylheku.com (Kaz Kylheku) (2014-06-21)
Re: Formatting of Language LRMs Pidgeot18@verizon.net.invalid (=?UTF-8?B?Sm9zaHVhIENyYW5tZXIg8J+Qpw==?=) (2014-06-22)
Re: Formatting of Language LRMs mertesthomas@gmail.com (2014-06-30)
Re: Formatting of Language LRMs ivan@ootbcomp.com (Ivan Godard) (2014-07-03)
Re: Formatting of Language LRMs federation2005@netzero.com (2014-07-28)
Re: Formatting of Language LRMs federation2005@netzero.com (2014-08-01)
Re: Formatting of Language LRMs gah@ugcs.caltech.edu (glen herrmannsfeldt) (2014-08-03)
| List of all articles for this month |
From: glen herrmannsfeldt <gah@ugcs.caltech.edu>
Newsgroups: comp.compilers
Date: Sun, 3 Aug 2014 04:37:37 +0000 (UTC)
Organization: Aioe.org NNTP Server
References: 14-06-010 14-06-013
Keywords: parse, tools
Posted-Date: 03 Aug 2014 14:01:58 EDT

lpsantil@gmail.com <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]




Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.