Talk:Parse EBNF: Difference between revisions
Content added Content deleted
(→ANTLR parser EBNF or ISO standard EBNF?: and ideas for a →Rewrite?: .) |
|||
Line 37: | Line 37: | ||
== PicoLisp grammar is PicoLisp not EBNF == |
== PicoLisp grammar is PicoLisp not EBNF == |
||
PicoLisp seems to parse PicoLisp rather than EBNF. This makes for a shorter program, but, if allowed, then the task description should state something like ''"parse an EBNF-like input grammer expressed as code for your programming language"'' to be fair. --[[User:Paddy3118|Paddy3118]] 05:05, 13 May 2011 (UTC) |
PicoLisp seems to parse PicoLisp rather than EBNF. This makes for a shorter program, but, if allowed, then the task description should state something like ''"parse an EBNF-like input grammer expressed as code for your programming language"'' to be fair. --[[User:Paddy3118|Paddy3118]] 05:05, 13 May 2011 (UTC) |
||
== ANTLR parser EBNF or ISO standard EBNF? == |
|||
There is a [http://www.cl.cam.ac.uk/~mgk25/iso-14977.pdf difference]. --[[User:Paddy3118|Paddy3118]] 05:43, 13 May 2011 (UTC) |
|||
== Rewrite?== |
|||
How about defining an EBNF-like language here and have the task be to: |
|||
# Parse a ''given'' language definition for a simple calculator that goes right down to terminals. |
|||
# Parse a given expression including numbers with all digits and traversing all edges in the language graph. |
|||
# Parse a modified language definition where NUMBERS do not include 6. |
|||
# Print and show that the earlier expression fails to parse. |
|||
--[[User:Paddy3118|Paddy3118]] 05:43, 13 May 2011 (UTC) |