-
Notifications
You must be signed in to change notification settings - Fork 1
Comparison of jdsl and parboiled
Peter Verhas edited this page Jan 23, 2014
·
1 revision
parboiled is an analyzer tool that has similar goals as that of jdsl. The major difference between jdsl and parboiled is that jdsl is simpler in API and in its internals. There are no magic proxy objects created, there is no need for any annotation or any annotation processor. jdsl is simply a library of simple Java classes. Having said that this page is to compile a table of comparison.
jdsl | parboiled | ||
Java | yes | yes | Both solutions are implemented using Java. Parboiled supports Scala providing special scala specific features. Jdsl, though can be used as a library from any JVM language does not deliver any specific non-Java language feature. This also means that you will need SBT to build parboiled. To build jdsl you need Java and maven. |
proxy | no | yes | In parboiled you define your grammar rules creating methods. In Jdsl you define grammar rules as objects calling jdsl fluent api. Since grammars are usually recursive parboiled grammars are defined with recursive methods that would execute until the stack is full. To provide exit condition parboiled creates proxy classes and the instance objects on the fly using the ASM library. Jdsl does not generate classes and has no external dependencies, except logging. |
annotation | no | yes | Jdsl does not use any annotation. To use parboiled you create classes and methods that are annotated. |
maturity | new | mature |