Talk:Parse EBNF: Difference between revisions

From Rosetta Code
Content added Content deleted
(Need to better define the task)
Line 5: Line 5:


The task wording is somewhat sloppy. A parser could be for a (EBNF) grammar, not (plural) grammars. For grammars there can be a parser generator. The existing examples in fact build a parser for a particular grammar, and they don't use EBNF at all. May be task should be renamed as "Simple calculator parser"?[[User:Avmich|Avmich]] 20:30, 22 April 2011 (UTC)
The task wording is somewhat sloppy. A parser could be for a (EBNF) grammar, not (plural) grammars. For grammars there can be a parser generator. The existing examples in fact build a parser for a particular grammar, and they don't use EBNF at all. May be task should be renamed as "Simple calculator parser"?[[User:Avmich|Avmich]] 20:30, 22 April 2011 (UTC)

== EBNF parser or parser for the given EBNF grammar? ==

Is the task to write a parser that takes an EBNF grammar as input? That's how the task description sounds for me, but all implementation examples don't do this..
Or is the task to write a parser for the given EBNF grammar? Then the description should be clarified and the title changed.
None of the examples parses the EBNF grammar.
--[[User:Oenone|Oenone]] 11:48, 10 May 2011 (UTC)

Revision as of 11:48, 10 May 2011

I guess I started this as a draft task because I haven't implemented it myself yet.
There is no reason to keep it a draft too long if we get a few fresh implementations here. Tinku99 05:28, 12 June 2010 (UTC)tinku99

Interesting. I usually create a task after having an implementation as it helps with the task description etc. --Paddy3118 10:31, 12 June 2010 (UTC)

The task wording is somewhat sloppy. A parser could be for a (EBNF) grammar, not (plural) grammars. For grammars there can be a parser generator. The existing examples in fact build a parser for a particular grammar, and they don't use EBNF at all. May be task should be renamed as "Simple calculator parser"?Avmich 20:30, 22 April 2011 (UTC)

EBNF parser or parser for the given EBNF grammar?

Is the task to write a parser that takes an EBNF grammar as input? That's how the task description sounds for me, but all implementation examples don't do this.. Or is the task to write a parser for the given EBNF grammar? Then the description should be clarified and the title changed. None of the examples parses the EBNF grammar. --Oenone 11:48, 10 May 2011 (UTC)