You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Kyungho Jeon (JIRA)" <ji...@apache.org> on 2014/06/06 05:56:02 UTC
[jira] [Commented] (PIG-2597) Move grunt from javacc to ANTRL
[ https://issues.apache.org/jira/browse/PIG-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019544#comment-14019544 ]
Kyungho Jeon commented on PIG-2597:
-----------------------------------
Sorry that I hasn't been quite active. :( I think I am confused with the above comment by [~daijy] regarding Macro. I find a test case in the workaround (PIG-3359). Would it be good enough for me to design based on the test case, or is there any other cases that the test case does not cover?
> Move grunt from javacc to ANTRL
> -------------------------------
>
> Key: PIG-2597
> URL: https://issues.apache.org/jira/browse/PIG-2597
> Project: Pig
> Issue Type: Improvement
> Reporter: Jonathan Coveney
> Assignee: Daniel Dai
> Labels: gsoc2014
> Attachments: pig02.diff
>
>
> Currently, the parser for queries is in ANTLR, but Grunt is still javacc. The parser is very difficult to work with, and next to impossible to understand or modify. ANTLR provides a much cleaner, more standard way to generate parsers/lexers/ASTs/etc, and moving from javacc to Grunt would be huge as we continue to add features to Pig.
> This is a candidate project for Google summer of code 2014. More information about the program can be found at https://cwiki.apache.org/confluence/display/PIG/GSoc2014
--
This message was sent by Atlassian JIRA
(v6.2#6252)