Re: [cilib-devel] [PATCH 0/3] Replacement of Domain string parser.

[Theuns C. <the...@gm...>]

Hey Gary,

Would it make sense to split the parser into a separate maven module?
This way the parser code only has to be generated once, and the JAR
file can just be included in the classpath.

Regards
--
Theuns

On Wed, Jun 10, 2009 at 12:51 PM, Gary Pampara<gpa...@gm...> wrote:
> The need to have a decent parser for the domain strings is something
> that has been on the cards for a very long time. The main problem with
> the current implementation is that it is very non-expressive.
>
> Illegal domains such as:
>  - R(8, 9)^-1
>  - R^0
>  - Any other strange combination
>
> were allowed in the previous parser.
>
> These patches propose a new generated parser based on a provided grammar
> file.
>
> JJTree and JavaCC were used to achieve the parser.
>
> Gary Pampara (3):
>  Semi-complete parser definition.
>  Deprecation of parser for generated parser.
>  Prevent invalid values / options in domain strings.